Skip to main content
Glama
TweetAPI MCP

TweetAPI MCP

Official

Search TweetAPI Docs

tweetapi_docs_search
Read-onlyIdempotent

Search TweetAPI public documentation by keyword to find matching sections with titles, snippets, source URLs, and scores for questions about pricing, limits, errors, or authentication.

Instructions

Search TweetAPI's public docs by keyword and return the best-matching sections, each with a title, a short snippet, its source URL and a score. Use it for general questions such as pricing, limits, errors or authentication; for one endpoint's full reference, use tweetapi_docs_get_page. Free: reads the public docs and uses no API key or units.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "tweetapi_docs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many matching sections to return, 1 to 10. Default 5.
queryYesWords to look for in the docs, such as rate limits, pagination or followers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.3
    • addedInput schema / properties / limit / description
      Added value: +"How many matching sections to return, 1 to 10. Default 5."
    • addedInput schema / properties / query / description
      Added value: +"Words to look for in the docs, such as rate limits, pagination or followers."
  2. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond them by stating the tool is free and needs no API key or units, plus the shape of each returned match. It does not discuss result quality thresholds or what happens on zero matches.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and return shape, followed by usage routing and the cost note. Nothing redundant.

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

Completeness5/5

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

No output schema exists, and the description compensates by listing the returned fields. Combined with the explicit alternative sibling and the zero-cost note, an agent has everything needed to call this correctly.

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 coverage is 100% and both parameters are documented with ranges and a default for limit, so the schema carries the burden. The description only implies keyword matching and ranking by score; it adds little beyond 'best-matching', so baseline 3 applies.

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

Purpose5/5

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

Specific verb and resource: 'Search TweetAPI's public docs by keyword' with explicit statement of what comes back (title, snippet, source URL, score). It is clearly differentiated from the sibling tweetapi_docs_get_page, which it names.

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

Usage Guidelines5/5

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

Explicit when-to-use ('general questions such as pricing, limits, errors or authentication') and when-to-use-the-alternative ('for one endpoint's full reference, use tweetapi_docs_get_page'). No inference required.

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