Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

mastodon_account_statuses

List a Mastodon account's public statuses by acct or id with instance, using max_id to page to older posts. Returns one page of public statuses for account research and monitoring.

Instructions

mastodon: List an account's statuses. GET /v1/mastodon/account/statuses. Provide one of: acct, id. One page of public statuses. Pass acct, or id together with instance. max_id is the older-than cursor. An empty page costs 0 credits. Costs 1 credit when it succeeds. Costs 0 credits when statuses is empty. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mastodon_account_statuses"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAccount id on the instance, used with instance instead of acct.
acctNoAccount in the form user@instance.
max_idNoReturn statuses older than this id.
instanceNoInstance hostname. Required when id is used instead of acct.
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

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: results are one page of *public* statuses only, max_id is the older-than cursor, and the credit-charging rules are spelled out (1 credit on success, 0 on empty/error/cache hit). It omits whether authentication is required and whether forward pagination exists beyond max_id.

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

Conciseness3/5

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

Front-loaded correctly with purpose, endpoint, and identifier rules, but the credit-cost explanation is inflated: 'An empty page costs 0 credits', 'Costs 0 credits when statuses is empty', and the empty/not-found caveat repeat the same information across three sentences. Tightening to one cost sentence would lose nothing.

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 five-parameter read tool with no annotations and no output schema, the description covers the essentials an agent needs: identifier forms, cursor direction, result scope (one page of public statuses), and billing behavior. The remaining gap is auth/permission requirements and what fields a status object contains, which an agent must discover elsewhere.

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%, so the schema already documents all five parameters including the acct-vs-id/instance relationship. The description's restatement ('max_id is the older-than cursor', 'Pass acct, or id together with instance') reinforces the mutual exclusivity but adds little syntax or format detail beyond the schema. Baseline 3 applies.

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?

Names a specific verb and resource ('List an account's statuses') and pins it to the endpoint GET /v1/mastodon/account/statuses, so it is distinguishable from mastodon_status (single status) and mastodon_profile. It stops short of explicitly naming which sibling to use for related lookups, so it is clear but not sibling-routing.

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?

Gives concrete input routing ('Provide one of: acct, id', 'Pass acct, or id together with instance'), which is genuine when-to-use guidance at the parameter level. It never states when to prefer this over mastodon_profile or mastodon_hashtag, nor mentions auth or rate-limit preconditions, so the guidance is implied rather than explicit.

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