retweet
Retweet a specific tweet by providing its numeric ID.
Instructions
Retweet a tweet.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tweet_id | Yes | The numeric tweet ID to retweet. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Retweet a specific tweet by providing its numeric ID.
Retweet a tweet.
| Name | Required | Description | Default |
|---|---|---|---|
| tweet_id | Yes | The numeric tweet ID to retweet. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations available, the description fully bears the burden of disclosing behavioral traits. It offers none, such as whether the action is reversible, if authentication is needed, or any side effects.
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 very concise at three words, but it lacks structure and depth. It is front-loaded with the action, but fails to provide any additional context that would aid an AI agent.
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?
Given the tool's simplicity (one parameter, output schema present), the description is too minimal. It does not include information about reversibility, authentication, or when to use, leaving significant gaps for an agent.
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?
The schema covers the single parameter 'tweet_id' with a clear description. The main description adds no further meaning to the parameter, so it meets the baseline for 100% schema coverage.
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?
The description clearly states the verb 'Retweet' and resource 'a tweet', directly indicating the action. It distinguishes from sibling tools like 'like_tweet' or 'unretweet' by naming the specific action.
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?
No guidance is provided on when to use this tool versus alternatives such as 'post_tweet' or 'unretweet'. There is no mention of prerequisites, context, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pranrichh/spectre-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server