Skip to main content
Glama

Visibility Genies

Read drafts

get_saved_drafts
Read-only

Reads the drafts saved in the Writing Assistant: each with its title, the content template it follows, its word count, its match with the top pages out of 100 against that template (the share of the terms most of the pages that rank use that it covers; length, headings and readability are not part of it), and when it was saved (updatedAt); or one draft's text, its match, what to do next, and the tone and originality notes saved for it. A draft names the brief Content Creation wrote it from, and when an agent last saved it with save_draft. Uses no credits and calls no provider. save_draft saves an article you wrote; no agent tool buys notes: the page does, pricing each run first.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_saved_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdNoThe draft to read, from this tool's list. Omit to list the project's drafts.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
draftYes
draftsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/destructive annotations, it discloses that the call consumes no credits and contacts no provider, which is genuinely useful cost information for an agent deciding whether to call. It also describes the shape of each response mode (list fields versus single-draft fields, including updatedAt). The dangling remark about notes and pricing is confusing but not contradictory.

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

Conciseness2/5

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

The definition is one long, comma-chained paragraph with deep parentheticals about match scoring ('the share of the terms most of the pages that rank use that it covers; length, headings and readability are not part of it'). The final sentence about notes, pages, and per-run pricing is largely irrelevant to reading a draft. Structure is poor and much of the wording does not earn its place.

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 an output schema present, the return values did not need narrating, yet the description covers both modes adequately and adds the zero-credit behavior an agent would want to know. The tool is simple (two params, no nesting, closed world), and nothing essential is missing — only the noisy pricing tangent detracts.

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 both parameters are already documented, including the projectId billing note and draftId's 'omit to list' behavior. The description restates the same semantics rather than adding new ones. Baseline 3 is appropriate since the schema carries the load.

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 first sentence names a concrete verb and resource ('Reads the drafts saved in the Writing Assistant') and clearly separates two modes: a project-level list versus a single draft's text. It further distinguishes itself from 'save_draft' by stating what that sibling does. The purpose is unmistakable, though the parenthetical clutter about match scoring and credits makes it slower to parse than it needs to be.

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

Usage Guidelines4/5

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

It states the condition that switches modes — 'Omit [draftId] to list the project's drafts' — and where the draftId comes from ('from this tool's list'). It also names the write counterpart, save_draft, implying this tool is for reading existing drafts. It stops short of explicit when-not-to-use guidance or prerequisites beyond what the schema already says.

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