Skip to main content
Glama

Create content briefs

content.brief

Generates up to three content briefs for a website project to help plan focused topics before writing. Use it for small brief sets when broader content planning is not required.

Instructions

Specialized: at most three content briefs. Prefer qualitykit.plan.

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": {
      "projectRoot": "<projectRoot>"
    },
    "name": "content.brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlNo
maxBriefsNo
projectRootYesAbsolute path to the website repository root

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses a maximum of three briefs, but says nothing about whether briefs are created or written, permissions, side effects, or output; the cap largely repeats maxBriefs.

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

Conciseness3/5

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

Two terse fragments with no wasted words, and the cap and alternative are front-loaded. However, the terseness tips into under-specification rather than efficient structure.

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

Completeness2/5

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

For a no-annotation creation tool with three parameters and no output schema, this is too sparse: no explanation of what a brief contains, prerequisites, or expected result. The only context is a cap and a sibling preference.

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

Parameters2/5

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

Schema coverage is 33%, with only projectRoot described. The description reinforces the maxBriefs cap already in the schema but doesn't explain siteUrl, projectRoot's role, or how maxBriefs interacts with the brief count.

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

Purpose3/5

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

Names the resource (content briefs) and a hard scope cap, but omits an explicit verb; the action must be inferred from the title 'Create content briefs'. It does distinguish itself partly by directing agents to qualitykit.plan.

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?

Provides one routing instruction—prefer qualitykit.plan—but doesn't state when this tool is the right choice or what 'specialized' means. The agent knows an alternative exists but not the selection criteria.

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