Skip to main content
Glama

The Marketing Vault

Improve existing copy

improve_existing_copy

Critiques and rewrites existing text, matches a human voice or removes filler. Output is saved to the Library and uses one generation. Nothing is sent or published.

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": {
      "template": "<template>",
      "details": "<details>"
    },
    "name": "improve_existing_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailsYesWhat the user wants, including supplied source text, goals or constraints.
templateYescritique-and-rewrite: Critique and rewrite existing copy. human-voice-rewrite: Rewrite text in a human voice. distill-remove-fluff: Distill text and remove AI filler.
existing_copyNoExisting copy for the selected template.
critique_focusNoCritique focus for the selected template.
content_to_distillNoContent to distill for the selected template.
content_to_rewriteNoContent to rewrite for the selected template.
business_profile_idNoBusiness profile id. Required when the account has multiple Businesses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare openWorld=false, destructive=false, and non-idempotent. The description adds genuinely new behavioral facts: output is persisted to the Library, consumes one generation, and nothing is sent or published. That last point is valuable reassurance for a mutation tool whose readOnlyHint is false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with zero filler; the capability comes first and the side-effect/safety caveat follows. Every clause carries information.

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

Completeness4/5

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

With seven parameters, an enum, and no output schema, the description covers the action, the persistence destination, and the cost/safety profile adequately. It could say more about how the required 'details' field interacts with the template-specific content fields, but the schema carries that.

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%, so the template enum values and each content field are already documented in the schema. The description adds no mapping of which content field pairs with which template, so baseline 3 applies.

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?

States specific verbs and resources: critiques and rewrites existing text, matches human voice, removes filler. The focus on 'existing' text implicitly separates it from the write_* sibling family that produces new copy, though no sibling is named explicitly.

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?

The word 'existing' implies this is for revising supplied text rather than drafting from scratch, and the three template names hint at sub-modes. However, it never states when to pick this over write_ad_copy or write_email_copy, nor any prerequisites.

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