Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

mastodon_hashtag

Retrieve one page of a public Mastodon hashtag timeline from a specified instance; use max_id to fetch older statuses.

Instructions

mastodon: Hashtag timeline. GET /v1/mastodon/hashtag. One page of the public tag timeline on instance. 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

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": {
      "hashtag": "<hashtag>",
      "instance": "<instance>"
    },
    "name": "mastodon_hashtag"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_idNoReturn statuses older than this id.
hashtagYesTag name, with or without a leading #.
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

A3.7/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 it does unusually well on the cost dimension: success costs 1 credit, empty statuses cost 0, cache hits and errors/timed-out/blocked requests cost nothing. What it omits is auth requirements, rate limits, and any indication of what a 'page' contains or how to advance 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.

Conciseness2/5

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

The purpose is front-loaded and effective, but the billing block is redundant: 'An empty page costs 0 credits', 'Costs 0 credits when statuses is empty', and the closing sentence about not-found/empty results restate the same rule three ways. The final sentence is also ambiguous enough to undercut the clarity of the preceding cost statements.

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?

For a 4-parameter read endpoint with no output schema and no annotations, the definition covers cost and pagination entry points but says nothing about the shape of returned statuses, auth needs, or instance-level constraints. An agent could call it, but not predict the response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% – every parameter (hashtag, instance, max_id, cache_max_age) has its own documented semantics including examples. The description correctly leaves parameter explanation to the schema rather than duplicating it.

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 description names a specific resource and action: 'Hashtag timeline. GET /v1/mastodon/hashtag', refined by 'One page of the public tag timeline on instance'. An agent immediately knows this retrieves public posts for a tag on a given instance. It does not explicitly separate itself from sibling timeline tools such as mastodon_account_statuses, which keeps it out of 5 territory.

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 implied by 'public tag timeline on instance' and by the schema's max_id/cache_max_age fields, but there is no explicit statement of when to pick this over an account-status tool or when a hashtag lookup is inappropriate. No prerequisites or exclusions are given.

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