Skip to main content
Glama

XCROP X (Twitter) data

Check a repost, reply or quote

check_interaction
Read-only

Did an account repost, reply to or quote a given X post? Built for giveaway, airdrop and quest verification. For reply and quote, min_tags requires that many @mentions in the text. Costs 50 credits.

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": {
      "tweet_id": "<tweet_id>",
      "username": "<username>",
      "action": "<action>"
    },
    "name": "check_interaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhich interaction to check
min_tagsNoreply/quote only: minimum @mentions required
tweet_idYesNumeric tweet (post) id, or the full post URL
usernameYesThe account to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description only needed to add context beyond that, and it does: a concrete cost of 50 credits and the conditional rule that min_tags applies only to reply and quote. It stops short of disclosing rate limits, failure modes, or what happens when the account or post does not exist.

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, front-loaded with the core question, then the use case, then the cost. Every sentence carries information an agent can act on, with no repetition of the schema.

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 read-only verification tool with four fully documented parameters, the definition covers purpose, scope of min_tags, and cost. The main residual gap is that no output schema exists and the description never states the return shape (a boolean versus an object with match details), which an agent might want before relying on the result.

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% and the enum on action is documented, so the structured fields already carry parameter meaning. The description only restates the min_tags constraint (reply/quote only) that the schema itself already states, adding no new syntax or format detail, so the baseline of 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?

'Did an account repost, reply to or quote a given X post?' states a specific verb-per-action and resource, and the boolean framing ('Did an account...') distinguishes it from listing siblings such as get_tweet_retweeters and get_tweet_replies, which return sets of accounts rather than a yes/no for one account.

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

Usage Guidelines3/5

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

It supplies a concrete usage context ('giveaway, airdrop and quest verification'), which helps an agent recognize the intended scenario, but it names no alternative and gives no when-not guidance. An agent must infer on its own that listing tools should be used when the goal is enumerating interactors rather than verifying one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources