Skip to main content
Glama

get_email_campaign_run

Read-onlyIdempotent

Read a campaign review or send run and its delivery counts in the approved business.

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": {
      "id": "<id>"
    },
    "name": "get_email_campaign_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds useful behavior beyond that: the response includes delivery counts and the lookup is constrained to 'the approved business'. It does not explain what distinguishes a review run from a send run or what happens if the id is not found.

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?

A single front-loaded sentence with no filler. The wording 'campaign review or send run' is a bit compressed and could be clearer, but nothing is wasted.

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, read-only lookup with no output schema, the description does state the key return content (delivery counts), which is the main thing an agent would otherwise miss. It leaves open the shape of those counts, the review-vs-send distinction, and error behavior for an unknown id, so it is adequate but not complete.

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?

There is one required uuid parameter with 0% schema description coverage; the pattern and format in the schema convey the type, but nothing states that the id identifies a campaign run specifically. The description implies the lookup target but adds no meaning about the identifier beyond what the schema already encodes.

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 uses a specific verb ('Read') with a specific resource ('campaign review or send run') and notes it returns delivery counts, so the agent can tell this is a single-run read rather than a listing. It stops short of naming or contrasting with the sibling list_email_campaign_runs, and the phrase 'review or send run' is slightly ambiguous about whether these are two run types.

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?

There is no explicit when-to-use guidance, no mention of when to prefer list_email_campaign_runs or get_email_campaign_draft, and no stated prerequisites. The clause 'in the approved business' hints at a workspace/account scoping prerequisite but does not spell it out.

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