manychat_tag_subscriberAdd a specified tag to a ManyChat subscriber by tag name. Use this to organize subscribers when the tag already exists.
Add a tag to a subscriber by tag name. The tag must already exist.
| Name | Required | Description | Default |
|---|---|---|---|
| tag_name | Yes | Tag name to add | |
| subscriber_id | Yes | ManyChat subscriber ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey that this is a non-read-only, non-destructive operation, and the description adds the precondition but doesn't cover error cases, duplicate-tag behavior, or response effects. This is adequate but not rich behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no filler; the main action is front-loaded and the precondition earns its place. Nothing extraneous.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter mutation with basic annotations, the description plus schema covers the essentials needed to call the tool. It stops short of stating what happens if the tag doesn't exist or whether the operation is idempotent, which would make it fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents both parameters with 100% coverage. The description adds meaning by clarifying that tag_name must reference an already-existing tag, which is useful semantic context beyond the raw schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: add a tag to a subscriber by tag name. It also gives the key precondition that the tag must already exist, which helps distinguish it from related siblings like manychat_create_tag and manychat_untag_subscriber.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It communicates when the tool is valid by requiring an existing tag, and thus implicitly suggests creating the tag first if needed. It doesn't explicitly name sibling tools or state when not to use it, so it falls just short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.