Skip to main content
Glama

Content brief

content_brief

The research for one page: facts with their source URLs (read from the pages that rank and the pages AI engines cite), the headings those pages cover, People Also Ask, the gaps none of them answers, an outline, and the rules the page is checked against. You write the page in the repo from this; every number must come from a fact. Costs $0.10 from the balance, charged only when it returns.

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": {
      "type": "<type>",
      "topic": "<topic>"
    },
    "name": "content_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesglossary_term, answer_page, comparison (topic = the rival), alternatives (topic = the rival), article
topicYesThe term, the question, the rival's name, or the article's title
keywordNoThe target keyword, when it differs from the topic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description adds genuinely useful behavior beyond annotations: the $0.10 charge, the 'charged only when it returns' billing rule, and the fact that sources are drawn from ranking pages and pages AI engines cite (reinforcing openWorldHint=true). It does not conflict with readOnlyHint=false. However, it says nothing about latency, failure modes when the balance is insufficient, or what an empty/thin result looks like.

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 sentences, front-loaded with the deliverable list and closed with the writing constraint and the price. The parenthetical about where facts are read from is dense but earns its place; the 'every number must come from a fact' rule is a downstream constraint rather than tool behavior, but it is short enough not to be bloat.

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 no output schema, the description carries the burden of explaining the return value and does so thoroughly by enumerating the brief's components. Cost and billing semantics are covered, so an agent knows what it gets and what it pays; only failure/insufficient-credit behavior is unaddressed.

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 coverage is 100%, with enum values and per-parameter descriptions already documenting type, topic, and keyword. The description adds only framing ('one page', 'the rival' semantics implied by type), so the schema does the heavy lifting; 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?

The description enumerates exactly what the tool produces: facts with source URLs, competitor headings, People Also Ask, gaps, an outline, and the rules the page is checked against. It also implicitly scopes the tool as research-only ('You write the page in the repo from this'), which separates it from a content-writing or checking tool, though it never names siblings like research or check_content.

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?

Usage is implied rather than stated: 'You write the page in the repo from this' tells the agent this is the pre-writing step for a single page. There is no explicit when-to-use/when-not guidance, no mention of how it differs from the sibling 'research' tool, and no prerequisites such as sufficient balance beyond the cost note.

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