Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

add_task_follower

Add a teammate as a follower of a task, or remove them with remove:true. The user must already be a board member; the call is idempotent.

Instructions

Add a teammate as a follower of a task, or drop them with remove:true. The user is an email or a user UUID and has to be a member of that board already; adding one sends the same notification the app does, and the call is idempotent.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does well: it discloses the notification side effect, idempotency, and the board-membership prerequisite. It does not describe permission requirements beyond board membership or error behavior, but the important side effects are covered.

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 a single dense sentence that front-loads the main action, then adds the inverse operation, prerequisite, side effect, and idempotency. Every clause adds useful information without repetition.

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 description covers the key behavioral facts well, but because the formal schema is an empty object, the agent lacks structured parameter names and types for the task, user, and remove flag. It is adequate but leaves a meaningful gap for invocation correctness.

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 input schema is effectively empty, so the description must carry all parameter meaning. It explains that the user can be an email or a user UUID and that remove:true drops the follower, which is valuable. It is less explicit about how the task itself is identified, but the core parameter semantics are present.

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?

The description states a specific verb and resource: adding a teammate as a follower of a task, with an explicit inverse operation via remove:true. It does not name a sibling tool for differentiation, but the purpose is unambiguous.

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?

It gives a clear prerequisite (the user must already be a member of the board) and explains the removal alternative, which is useful when-to-use context. It does not address when to prefer this over related actions such as commenting or assigning, but that is a minor gap.

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