Skip to main content
Glama

FoxAPIs data sources

Mastodon post

mastodon_post
Read-onlyIdempotent

A Mastodon post: text, author, likes, reposts, replies and time, from its link. Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": {
      "url": "<url>"
    },
    "name": "mastodon_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://mastodon.social/@Gargron/1"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-structural context: a 2-credit cost per call, no charge when the answer has no data, and the need for a FoxAPIs key. It stops short of describing failure modes (private/deleted posts, rate limits) but the billing and auth details are real added value.

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?

A single dense sentence, front-loaded with what the tool returns, then cost and auth in short clauses. Every clause carries information and there is no filler.

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 one-parameter read-only fetch with no output schema, the description covers the returned fields, billing and auth prerequisites. Only error/edge-case behavior (deleted or private posts) is left unstated, a minor gap given the annotations.

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?

With a single parameter and 100% schema coverage including an example URL, the schema carries parameter meaning. The description only reinforces that the input is a post link, adding no format or constraint detail beyond what is already documented.

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 (a Mastodon post) and enumerates the fields returned (text, author, likes, reposts, replies, time), plus the input basis (its link). That is enough to distinguish it from siblings like bluesky_post or github_repo without opening the schema, though it never uses an explicit verb such as 'fetch' or 'retrieve'.

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: 'from its link' signals that the tool needs a post URL, and the platform name narrows it to Mastodon. There is no statement of when to prefer it over platform siblings, nor any exclusion or prerequisite beyond the key note.

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