Skip to main content
Glama
TweetAPI MCP

TweetAPI MCP

Official

TweetAPI SDK Guidance

tweetapi_sdk_guidance
Read-onlyIdempotent

Returns SDK setup guidance for calling TweetAPI from Python or Node.js/TypeScript code: package name, install command, import example, and notes. Use when building an app; makes no API calls.

Instructions

Return setup guidance for calling TweetAPI from your own code: the SDK package name, install command, an import example and notes, for Python or Node.js/TypeScript. Use it when writing an app that calls TweetAPI; to fetch data now, use the live tools instead. Free: makes no API calls.

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": {
      "language": "<language>",
      "task": "<task>"
    },
    "name": "tweetapi_sdk_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesWhat the code should do, such as fetch a user's latest posts. It is echoed back.
languageYesProgramming language: Python, or Node.js, TypeScript or JavaScript.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.3
    • addedInput schema / properties / language / description
      Added value: +"Programming language: Python, or Node.js, TypeScript or JavaScript."
    • addedInput schema / properties / task / description
      Added value: +"What the code should do, such as fetch a user's latest posts. It is echoed back."
  2. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this a non-destructive, idempotent, open-world read, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: it is free and makes no API calls, and it discloses the shape of the returned content. What it does not say is whether the guidance is static or reflects the current API version.

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 what is returned, then the routing condition, then the cost note. Nothing is padded and every clause carries information an agent would otherwise have to guess.

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?

There is no output schema, so the description correctly takes on the burden of describing return contents, and it does so for a simple two-string-input tool. The remaining gap is the undocumented effect of 'task' on the response beyond the schema's note that it is echoed back.

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 both parameters are already documented and the baseline is 3. The description adds little beyond the schema, and it actually narrows the language list to 'Python or Node.js/TypeScript' while the schema accepts JavaScript too — a small inconsistency rather than added meaning. The 'task' parameter is not mentioned at all in the description.

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?

States a specific verb and resource ('Return setup guidance for calling TweetAPI from your own code') and enumerates exactly what is returned: SDK package name, install command, import example and notes. It also names what it is not ('to fetch data now, use the live tools instead'), which separates it cleanly from the ~50 data-fetching siblings.

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?

Gives both sides of the routing decision: use this when writing an app that calls TweetAPI, use the live tools when you want data now. The only minor gap is that it does not point at the docs siblings (tweetapi_docs_get_page, tweetapi_docs_search), but the primary alternative is named explicitly.

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