Skip to main content
Glama

API Direct

by io.apidirect

search_forums

Search forum posts across the web.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-10 (default: 1). 10 posts per page
timeNoTime filter: "any", "hour", "day", "week", "month", or "year"any
queryYesSearch keyword (max 500 characters)
countryNo2-letter ISO country code, e.g. "us", "gb"
get_sentimentNoAdd AI sentiment analysis (Plutchik emotions, dominant_emotion, intensity, and positive/negative/neutral polarity) to each result. Adds a small per-page surcharge.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / page / description
      Previous value: -"Page number for pagination (default: 1)"New value: +"Page number, 1-10 (default: 1). 10 posts per page"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of disclosing behavior, but it only says 'Search forum posts across the web.' It does not mention result formatting, pagination behavior, the country/time filtering effect, or the get_sentiment surcharge described in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no filler or redundancy. It is concise, though it may be too sparse for a tool with five parameters and no annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, no annotations, no output schema, and a broad sibling family, a one-line description is not complete enough. It lacks usage context, edge-behavior notes, and any indication of what distinguishes forum search from other web/social searches.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all five parameters. The description adds no parameter meaning beyond the schema, which is acceptable but not additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Search') and resource ('forum posts') with a scope ('across the web'), so an agent can understand the basic function. It does not differentiate from closely related siblings like search_reddit or search_web, so it misses the distinction test.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no exclusions, and no mention of alternative tools. Among many sibling search tools, an agent gets no help deciding between search_forums and search_reddit, search_web, or search_news.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All API Direct toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation4/5

Most tools are clearly scoped by platform and resource (e.g. search_twitter vs twitter_user_tweets vs twitter_tweet_details). A few pairs like twitter_tweet_comments vs twitter_user_replies or facebook_page_posts vs search_facebook_posts could cause minor confusion, but descriptions generally clarify the distinction.

Naming Consistency4/5

The dominant pattern is snake_case with a platform_prefix_resource suffix, and search_* consistently marks search operations. Minor deviations include noun-style names like amazon_best_sellers and place_photos, and the odd get_ skill/comments tools, but the overall convention is predictable.

Tool Count2/5

74 tools is far beyond the typical well-scoped MCP server, even for a multi-platform API aggregator. The breadth is justified by the many platforms covered, but an agent will face a very large action space, and this could reasonably be split into per-platform servers.

Completeness4/5

The server provides strong lifecycle coverage for its read-only domain: search, profile/details, posts, and engagement data across most platforms. Gaps exist for some platforms (e.g. no LinkedIn person profile, no Facebook event details, no Truth Social profile/search, no Reddit subreddit-specific tools), but the core workflows are well covered.

Resources