Skip to main content
Glama

Visibility Genies

Read content briefs

get_saved_content_briefs
Read-only

Reads the briefs saved in Content Creation: each with its keyword, title, state and the Writing Assistant draft written from it; or one brief's title, meta description, reader, search intent, angle, what the pages that rank cover and miss, and its outline with each heading's terms, target length and whether its text is written. Uses no credits and calls no provider. No agent tool writes a brief or runs Content Creation: the page does, pricing each run first. save_draft can replace the text of the draft written from a brief.

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_content_briefs"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
metaNo
briefYes
briefsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/not-destructive/closed-world, and the description adds genuinely non-redundant behavior: 'Uses no credits and calls no provider,' which matters for cost planning. It also clarifies that no agent tool can create a brief, preventing a failed attempt. It stops short of mentioning pagination or result limits for the list mode.

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?

Purpose and the two modes are front-loaded, and the trailing sentences on credits and write-path are short and substantive. The opening sentence is a long run-on enumerating the single-brief fields, which slightly hurts scannability but carries information.

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

Completeness5/5

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

For a two-parameter read-only tool with an output schema and full annotation coverage, nothing material is missing: mode selection, cost behavior, and the write-path boundary are all covered, and return-field details are backed by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains that briefId switches the response from a shallow list to a deep single-brief record with meta description, reader, search intent, angle, competitive page coverage and per-heading outline data. That return-shape consequence of the parameter is not in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource ('Reads the briefs saved in Content Creation') and explicitly distinguishes two modes: a list of briefs with keyword/title/state/draft, versus a single brief's full research detail including outline. An agent can tell exactly what comes back in each mode without opening the schema.

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?

Guidance is clear: omit briefId to list, supply it to read one in depth, and 'save_draft can replace the text of the draft written from a brief' routes editing to the correct sibling. The statement that no agent tool writes a brief or runs Content Creation usefully excludes a whole class of expected actions, though it does not name sibling read tools like get_saved_drafts as alternatives.

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