Skip to main content
Glama

Edit or approve personalized lines

spur_review_personalization

Edit per-channel copy/custom fields or approve saved records after reviewing them. Reviewed lines are preserved by generation. Does not send outreach.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-open-world mutation, so the description is not carrying the full burden. It still adds two real behavioral facts beyond the annotations: edits survive subsequent regeneration ('preserved by generation') and the tool never dispatches outreach. It does not explain what the approve branch does to the records or that approval is gated on explicit user consent (that lives only in the schema).

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?

Two short sentences, front-loaded with the action repertoire and closing with the scope limit. Nothing is padded, though 'Reviewed lines are preserved by generation' is vague enough that it could be stated more precisely.

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?

This is a dual-mode tool with a oneOf schema, a hard confirm gate, and batches up to 5000 ids; the description covers the two modes but not the approval requirement or the scale of the approve branch. No output schema exists, so the description could reasonably say more about what is returned after an edit or approval.

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 description coverage is 100% at the structural level, so the baseline is 3. The description adds moderate meaning by mapping 'per-channel copy' to the variants object and 'custom fields' to custom_values, but it never clarifies the channel keys (sms/mail/email) or the field semantics (ps, cta, opener, reason, subject), and says nothing about the batch size or confirm flag.

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 two concrete verbs tied to the resource: 'edit per-channel copy/custom fields' and 'approve saved records'. This maps cleanly onto the two oneOf branches of the schema. It does not, however, explicitly distinguish itself from siblings such as spur_generate_personalization or spur_get_personalization, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'after reviewing them' implies a review-then-approve workflow, and 'Does not send outreach' rules out one wrong expectation. But there is no explicit when-to-use vs. when-not-to-use guidance and no named alternative for editing versus regenerating versus merely fetching personalization, so the routing is left to inference.

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