Skip to main content
Glama

pause_campaign

Pause an active marketing campaign to halt ongoing mass messaging temporarily.

Instructions

Pausar campana — Pausa temporalmente una campana de marketing masivo en curso [mutation]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesID de la campana a pausar
Behavior3/5

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

With no annotations, the description carries the burden. It correctly signals mutation via '[mutation]' and states 'temporalmente' implying reversibility, but does not disclose permissions, error states, or side effects (e.g., effect on schedule).

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?

The description is very concise (one line) and includes a helpful mutation tag. It is front-loaded but lacks structure like separate usage or behavior sections. Still, it efficiently conveys core purpose.

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 simple tool (1 param, no output schema), the description is adequate: it explains the action and effect. However, it lacks usage guidance and error context, and does not address relationships with sibling tools like resume_campaign.

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

Parameters3/5

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

Schema coverage is 100% with a clear description of campaign_id. The tool description adds no extra meaning beyond what the schema already provides, warranting a baseline score of 3.

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?

The description clearly states the action ('Pausar campana'), the resource ('campana de marketing masivo'), and the temporal nature ('temporalmente', 'en curso'). It distinguishes from siblings like cancel_campaign and resume_campaign by emphasizing temporary pause.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., cancel_campaign, archive_campaign) is provided. The description lacks conditionality or differentiation from related operations.

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/wazionapps/mcp-server'

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