Skip to main content
Glama
TweetAPI MCP

TweetAPI MCP

Official

Lookup TweetAPI Endpoint

tweetapi_endpoint_lookup
Read-onlyIdempotent

Find API endpoint documentation by path or keyword and return up to 10 matching snippets with source URLs, so you can identify the right endpoint and then view its full reference.

Instructions

Find the TweetAPI endpoint docs that match a path or keyword, and return up to 10 matching sections as snippets with their source URLs. Use it when you don't know the exact endpoint yet, then pass its path to tweetapi_docs_get_page for the full reference. Free: 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": {
      "pathOrKeyword": "<pathOrKeyword>"
    },
    "name": "tweetapi_endpoint_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathOrKeywordYesAn endpoint path such as /tw-v2/user/followers, or a keyword such as followers. A path gives the most precise match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.3
    • addedInput schema / properties / pathOrKeyword / description
      Added value: +"An endpoint path such as /tw-v2/user/followers, or a keyword such as followers. A path gives the most precise match."
  2. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the bar is low, yet the description adds real value: a result cap of 10, the snippet-plus-source-URL return format (no output schema exists), and 'Free: uses no API key or units' which discloses cost/auth requirements. Minor omission: no statement about result ranking or what happens when nothing 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?

Three short sentences, zero filler: what it does and what it returns, when to use it plus the follow-up call, then the cost/auth note. Front-loaded with the core capability.

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

Completeness4/5

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

For a single-parameter lookup with no output schema, the description supplies the return format, result limit, and cost profile, which is close to complete. It falls short only on disambiguating against tweetapi_docs_search in a 47-sibling toolset where that overlap is a real selection risk.

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 the schema already explains the path-vs-keyword distinction and that a path gives the most precise match. The description only echoes 'path or keyword', adding no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb+resource ('Find the TweetAPI endpoint docs') and the return shape (up to 10 matching sections as snippets with source URLs). However, it never distinguishes itself from the near-identical sibling tweetapi_docs_search, so an agent still has to guess between the two.

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

Usage Guidelines4/5

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

Explicitly states when to use it ('when you don't know the exact endpoint yet') and hands off to a named alternative (tweetapi_docs_get_page) for the full reference. The gap is that the competing docs_search sibling is not mentioned, so no exclusion rule exists for it.

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