Skip to main content
Glama

Followed people

list_people_follows
Read-only

Legacy alias of list_saved_alerts. The saved targets this account follows, with their latest episodes and alert settings. Free.

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": "list_people_follows"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds billing context ('Free') and hints at returned content (latest episodes, alert settings), but says nothing about pagination, result limits, or whether alias behavior differs from list_saved_alerts — the key thing an agent would want to know about an alias.

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?

Three short sentences/fragments, front-loaded with the most important fact (legacy alias). The trailing 'Free.' fragment is terse but informative; nothing is bloated. Minor cost: the middle sentence packs three concepts (targets, episodes, alert settings) without clarifying their relationship.

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 no parameters and no output schema, the description must carry the return-value picture, and it only sketches it ('latest episodes and alert settings') while leaving the people-vs-saved-targets confusion unresolved. For a zero-arg alias tool this is borderline adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics burden to carry. The description does not need to explain inputs and correctly doesn't attempt to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description calls it a 'legacy alias of list_saved_alerts' and then describes 'saved targets this account follows, with their latest episodes and alert settings' — but the tool name says 'people follows'. The mix of people-following, saved targets, and alerts makes the actual returned resource ambiguous, so an agent cannot cleanly tell what it gets back versus list_saved_alerts or list_follows.

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?

Labeling it a 'legacy alias' implies the agent should generally prefer list_saved_alerts and only use this for backward compatibility, but that routing is left to inference. There is no explicit when-to-use, when-not-to-use, or statement that results are identical to the aliased tool.

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