Skip to main content
Glama

Update draft

update_draft

Modify a draft's subject, body, importance or recipients before sending. Recipient lists replace existing ones, and an empty list clears them.

Instructions

Change a draft's subject, body, importance or recipients. Recipient lists replace the existing ones; an empty list clears them.

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": "update_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNoCc recipients: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
idYesDraft ID
toNoRecipients: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
bccNoBcc recipients: email addresses, either "jane@contoso.com" or "Jane Doe <jane@contoso.com>"
bodyNoMessage body
subjectNoSubject line
bodyFormatNoBody format: "text" (default) or "html"
importanceNoMessage importance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare the safe non-destructive write profile, and the description goes beyond them by disclosing that recipient lists overwrite rather than append and that an empty list clears recipients — a behavior not derivable from the schema. It still omits permission requirements, error behavior for a missing draft ID, and whether the update is partial.

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 short sentences, front-loaded with the scope and followed by the one non-obvious semantic rule. No filler and nothing redundant with the schema.

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 mutation tool with 8 optional-plus-one-required parameters and no output schema, the biggest open question is whether omitted fields are left untouched or reset — the description clarifies this only for recipient lists. The rest of the mutation contract (partial-update semantics, failure modes) remains unstated.

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 every parameter including the enum values for bodyFormat and importance is already documented. The description adds only the recipient-replacement rule; it says nothing extra about bodyFormat, importance, or how omitted fields behave.

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 gives a specific verb plus resource ("Change a draft") and enumerates the mutable fields (subject, body, importance, recipients), which is enough to separate it from create_draft and send_draft. It does not name a sibling explicitly, so it falls short of full differentiation, but the intent is unambiguous.

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?

Editing an existing draft is implied by "Change a draft's...", and the presence of create_draft/send_draft in the catalog makes the boundary reasonably inferable. However, there is no explicit when-to-use/when-not-to-use statement or pointer to alternatives, so the agent must infer routing.

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