Skip to main content
Glama
devrim-1283

truth-social-mcp

by devrim-1283

truth_followers

Read-onlyIdempotent

List followers for a Truth Social account with an authorized token. Returns follower details to analyze audience and engagement.

Instructions

List followers for an account. An authorized token is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
account_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds the useful context that an authorized token is required, which is not captured in the annotations. This provides meaningful behavioral information beyond the structured fields.

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?

The description is two short sentences, front-loaded with the primary action. Every word is useful, with no filler or redundancy.

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?

The tool is simple, and annotations plus the output schema provide solid context. However, the description does not discuss how this tool relates to sibling tools like 'truth_following' or clarify whether the token must belong to the queried account. This leaves some ambiguity in a broader workflow, making it adequate but not fully complete.

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 0%, so the description must compensate. It clarifies that 'account_id' refers to the account whose followers are listed, but it does not explain the 'limit' parameter or its effect on pagination/result count. The schema's default and constraints give some hints, but the description adds minimal value beyond the purpose.

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?

The description states 'List followers for an account' with a specific verb and resource, clearly distinguishing it from the sibling 'truth_following' which lists following accounts instead. This is a precise, unambiguous purpose.

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?

There is no guidance on when to use this tool versus alternatives. The description mentions that an authorized token is required, but it does not explain when this tool is appropriate (e.g., for viewing followers vs. following) or exclude any scenarios. No alternative tools are referenced.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/devrim-1283/truth-social-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server