Skip to main content
Glama
soil-dev

capsulemcp

batch_add_tag

Attach tags to multiple entities in a single batch, such as tagging 20 contacts after an event or updating 10 people with a 'Departed' tag. Processes up to 50 items in parallel to save time.

Instructions

Attach tags to many entities in parallel — e.g. tag a list of 20 contacts as 'RSAC26' after a conference, or apply the 'Departed' tag to 10 people in a layoff batch. Pass items: [{ entity, entityId, tagName }, ...] (1–50 items). Each item is processed identically to a single add_tag call. Connector fans out parallel HTTP requests, default cap 5 (CAPSULE_MCP_BATCH_CONCURRENCY). Returns { results: [{ok, ...} per item], summary: {total, succeeded, failed} }. The list_tags cache is invalidated for each affected entity type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesArray of 1–50 add_tag inputs. Useful for mass-tagging — e.g. 'tag these 20 contacts as RSAC26'. Each item is the same shape as a single add_tag call. The list_tags cache is invalidated for each affected entity type. Capped at 50.
Behavior4/5

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

Describes parallel fan-out, concurrency cap, return shape, and cache invalidation beyond annotations (which only show readOnlyHint false, destructiveHint false). No contradiction. Missing error behavior details but sufficient.

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?

Front-loaded with purpose and examples, then details. Every sentence adds value, though slightly long. Could trim wordiness but still efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a batch tool with no output schema, description covers return shape, limits, concurrency, per-item behavior, and cache effects. No gaps for typical usage.

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

Parameters5/5

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

Schema coverage is 100%, and description adds substantial meaning: for 'items' explains usage example and cache invalidation; for 'entity' clarifies legacy path; for 'tagName' details case sensitivity, idempotency, and resolution behavior. Greatly exceeds schema descriptions.

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?

Description clearly states batch tagging, provides concrete examples (RSAC26, layoff batch), and distinguishes from sibling 'add_tag' by noting each item is processed identically to a single add_tag call. Verb+resource+scope is specific.

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?

Explicitly says when to use (mass tagging, e.g., 20 contacts or 10 people), gives input format and limits (1–50 items), concurrency cap (5), and cache invalidation. Could explicitly mention to use add_tag for single tagging, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/soil-dev/capsulemcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server