x_organic_get_postRetrieves a specific post by ID with public metrics, author, media, and referenced posts to analyze engagement. Use this to fetch complete post details for organic Twitter management.
GET /2/tweets/:id with public metrics, author, media, and referenced posts.
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the description does not need to restate safety. It adds value by disclosing that the response expands to include public metrics, author, media, and referenced posts, which sets caller expectations. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with the core operation front-loaded. It contains no filler, and every element—endpoint, parameter, and returned data—contributes to understanding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter GET with read-only annotations, the description covers the operation, parameter, and key response components. It does not detail the exact output schema or error behavior, but that level of detail is not essential for selecting and invoking this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description carries the burden of clarifying the parameter. The route '/2/tweets/:id' identifies post_id as the tweet ID, and the title reinforces this, but no additional format details, examples, or edge-case constraints are provided beyond the schema's minLength.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states a specific operation ('GET /2/tweets/:id') and its resource, making it clear the tool fetches a single post by ID. It also lists returned components (public metrics, author, media, referenced posts), which differentiates it from plural lookup tools like lookup_posts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The name 'Get one post' and the endpoint imply it is for retrieving a single tweet by ID, but no explicit guidance is given about when to choose this over sibling tools. Alternatives and exclusions are not mentioned, so usage context is only inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.