Skip to main content
Glama

Unfollow a person

unfollow_person
Idempotent

Stop following a person. Needs the "account" scope. Free.

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": {
      "person": "<person>"
    },
    "name": "unfollow_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
personYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so the mutation and safety profile is covered structurally. The description adds genuinely new operational context — required auth scope and zero cost — but says nothing about what happens if the person isn't followed or what is returned.

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 very short sentences, action first, then constraints. Nothing is padded and nothing buries the lede.

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?

For a one-parameter toggle tool with no output schema this is close to adequate, but the identifier format for "person" and the outcome of unfollowing a non-followed account remain unspecified. Those are the two gaps an agent would actually hit.

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

Parameters2/5

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

Schema description coverage is 0% for the single parameter, and the schema only gives type string and maxLength 60. The description never clarifies whether "person" is a handle, an email, a UUID, or a profile URL — the one thing an agent most needs before calling.

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?

"Stop following a person" gives a specific verb (stop following) and resource (person), which cleanly separates it from the sibling unfollow_podcast. It stops short of an explicit contrast statement, but the resource noun does the disambiguating work.

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 description supplies a prerequisite (the "account" scope) and a cost note ("Free") but never says when to use this versus alternatives or what condition must hold — e.g. whether the person must currently be followed. No exclusions or routing guidance at all.

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