Skip to main content
Glama

Mastodon

by io.github.pipeworx-io

Search

search
Read-onlyIdempotent

Search Mastodon for accounts, statuses, or hashtags. Returns matching profiles, posts, and tags with follower counts and engagement metrics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoType of results: accounts, statuses, or hashtags (default: statuses)
limitNoNumber of results to return (default: 10, max: 40)
queryYesSearch query string

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesType of results returned: accounts, statuses, or hashtags
queryYesThe search query string used
accountsYesMatching Mastodon accounts
hashtagsYesMatching hashtags
statusesYesMatching posts/statuses

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the description need not repeat those. It adds that results include follower counts and engagement metrics, which provides useful behavioral context beyond the schema. However, it doesn't disclose any additional behavioral traits like rate limits or authentication needs.

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?

Description is a single efficient sentence with no wasted words. It front-loads the main purpose and adds output details concisely.

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?

Given the output schema exists, the description adequately covers return values by mentioning follower counts and engagement metrics. It could mention the default type (statuses) but the schema covers that. Overall complete for the tool's complexity.

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%, so the schema already details all parameters. The description does not add new parameter-level semantics beyond what the schema provides. The examples in the input schema are helpful but not part of the description.

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?

Description clearly states the tool searches Mastodon for accounts, statuses, or hashtags, specifying the resource and result types including profiles, posts, and tags with follower counts and engagement metrics. This distinguishes it from siblings like 'search_within' or 'deep_research'.

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?

Description implies usage for searching Mastodon content but does not explicitly state when to use this tool versus siblings like 'search_within' or 'deep_research'. No when-not guidance is provided.

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

All Mastodon toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is some overlap between research-oriented tools like ask_pipeworx and deep_research, and between entity_profile and compare_entities. Descriptions help differentiate them, so overall an agent can tell them apart.

Naming Consistency2/5

Tool names are inconsistent, mixing snake_case (ask_pipeworx, list_subscriptions) and camelCase (bag_research, compare_entities). There is no uniform naming pattern, which can be confusing.

Tool Count2/5

With 35 tools, the set is too large for a server named 'Mastodon'. Only a few tools are actually Mastodon-related (e.g., get_account, get_timeline), while the majority are PipeWorx tools unrelated to the core purpose.

Completeness1/5

As a Mastodon server, the toolset is severely incomplete: it lacks basic social media operations like posting statuses, following/unfollowing, and engaging with content. The name misrepresents the actual capabilities.

Resources