Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Mastodon hashtag

mastodon_hashtag_get
Read-onlyIdempotent

Fetch daily usage and account counts for a Mastodon hashtag from a specified server to assess tag activity.

Instructions

Get daily use and account counts for a Mastodon hashtag. Requires tag and host.

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": {
      "tag": "<tag>",
      "host": "<host>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "mastodon_hashtag_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYesRequired. Hashtag name without the `#`, e.g. `photography`. Letters of any script are allowed; the server folds case and accents.
hostYesRequired. The Mastodon server to ask, e.g. `mastodon.social`. A server URL is also accepted. The server you name is the one that answers.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only that the tool reports daily usage and account counts, with no mention of how many days are returned, freshness of the data, or rate-limit behavior on an open-world remote host.

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?

Two short sentences, front-loaded with what is returned, with no filler or hedging. The second sentence is largely redundant with the schema's required list, which keeps it from being maximally economical.

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?

With five parameters, four required, and no output schema, the description should describe the result shape, but 'daily use and account counts' leaves the window (how many days), units, and structure unspecified. It is adequate to start a call but not to anticipate the response.

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%, including the '#-less' tag form, host vs URL acceptance, and the analytics-only context/llm_model fields, so the schema does the heavy lifting. The description merely repeats that `tag` and `host` are required and adds no meaning beyond it, least of all for `context`, `llm_model`, or `conversation_id`.

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?

A specific verb and resource paired with the concrete payload: 'daily use and account counts' for a hashtag. That distinguishes it from list-style siblings such as mastodon_timeline_hashtag_list or mastodon_trends_hashtags_list, which return posts or trending tags rather than per-day statistics, though the description never names those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is the prerequisite 'Requires `tag` and `host`', which restates the schema rather than the situation that should select this tool. There is no statement of when to prefer this over the sibling hashtag/timeline tools, and no exclusions or error conditions.

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