Skip to main content
Glama
@jam-jam/convert-mcp

@jam-jam/convert-mcp

by titouannwtt

List the accounts that follow me

jj_list_followers

Lists your own followers newest first and shows pending follow requests when status is requested, so you can review accepted follows or requests without accessing anyone else's relations.

Instructions

Lists the calling account's own followers, newest first. status="requested" lists the follow requests it has not accepted yet. Only the caller's own relations are readable; reading somebody else's followers is not offered by this API.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jj_list_followers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, default 30, hard cap 100.
cursorNoOpaque cursor from a previous call's `nextCursor`. Replay it verbatim.
statusNo"accepted" (default) for established follows, "requested" for pending requests. Closed list: any other value is refused, the two states never mix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioural load: it discloses result ordering (newest first) and an access restriction (own relations only), which is genuinely useful. However, it says nothing about return payload shape, pagination behaviour, or authentication requirements, leaving meaningful gaps for a tool with no output schema.

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?

Three short sentences with zero redundancy: purpose and ordering first, then the status variant, then the access limitation. Every sentence contributes new information.

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 simple three-optional-parameter list tool with full schema coverage and no output schema, the description covers purpose, ordering, a key status mode, and the cross-account restriction. A brief note on pagination expectations would close the remaining gap.

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 limit, cursor, and status are already fully documented in the schema. The description restates the status='requested' meaning but adds no syntax, defaults, or edge-case detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource ('Lists the calling account's own followers'), adds ordering ('newest first'), and explicitly bounds scope by ruling out other users' follower lists. An agent can tell this apart from a generic listing tool without opening the schema.

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

Usage Guidelines4/5

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

Gives clear context for when the status='requested' variant applies (pending, unaccepted requests) and warns that other accounts' followers are not readable through this API. It stops short of naming any alternative tool for related listing needs, so it is clear but not fully routing.

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