Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

mastodon_status

Fetches a single public Mastodon status by ID from a given instance, returning HTML and tag-stripped text for content parsing, archiving, or moderation checks.

Instructions

mastodon: Fetch one status. GET /v1/mastodon/status. One public status by id on instance. HTML is returned as content and as text with tags removed. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "id": "<id>",
      "instance": "<instance>"
    },
    "name": "mastodon_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStatus id on the instance.
instanceYesInstance hostname.
cache_max_ageNoServe a cached response when it is newer than this. A cache hit costs 0 credits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does add real value: HTML returned both as raw content and tag-stripped text, plus a detailed cost model (1 credit on success, free on errors/timeouts/cache hits). However, it omits authentication or API-key requirements, rate limiting, and what a not-found response looks like beyond its cost.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the operation and endpoint, then return format, then cost. The cost sentences are somewhat repetitive ("costs nothing" details spread across three clauses) but each still carries distinct billing information an agent must know.

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

Completeness3/5

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

There is no output schema and no annotations, so the description must carry the load; it covers return format and billing but not auth requirements, error shapes, or visibility limits on non-public statuses. For a three-parameter read tool it is nearly adequate, but a couple of gaps remain.

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 each parameter already has a description and examples, so the schema does the documenting work. The description adds nothing about id format, instance hostname syntax, or how cache_max_age interacts with the cost model beyond what the schema states.

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?

The definition gives a specific verb and resource ("Fetch one status", "One public status by id on instance") and states the endpoint, so the agent knows exactly what it retrieves. It does not explicitly name the sibling it differs from (e.g., mastodon_account_statuses for lists), leaving that differentiation to be inferred from the word "one".

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?

Usage is only implied: fetching a single public status by id, with the constraint that only public statuses are reachable. There is no statement of when to prefer this over mastodon_account_statuses or what to do for private/authenticated statuses, and no prerequisites for obtaining a valid id.

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

Deploy Server

Other Tools