Skip to main content
Glama

Create a content brief

create_content_brief

Creates a search-informed content brief in Hi, Moose for one project: objective, audience, rationale, keyword buckets, recommended structure and constraints, grounded in live search results, the brand's own site crawl, brand guidelines and Brand Truth. Use it when the user wants a brief for a page or article on their site. Takes one to three minutes. Returns the brief as markdown plus structured fields and a briefId for create_draft. Give the returned brief to the user in full; they work from it here instead of opening Hi, Moose. When the brief starts from a row of visibility_list_opportunities, pass its opportunityId and the page URLs from the row's sources as referenceUrls: Hi, Moose then reads the pages the AI engines actually cited and uses them as reference sources for the 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": {
      "project": "<project>",
      "topic": "<topic>"
    },
    "name": "create_content_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe topic, question or working title the brief should cover. Up to 400 characters.
projectYesThe Hi, Moose project, by its name as shown by list_projects (for example "Hi, Moose"). The projectId is also accepted.
guidanceNoOptional: requirements already decided elsewhere (angle, must-include points, tone). Treated as requirements. Up to 4000 characters.
targetUrlNoOptional: the page on the brand's site this brief is for.
templateTypeNoOptional: the kind of content, for example "Blog post", "Landing page", "Comparison page", "Guide".
opportunityIdNoOptional: the opportunity id from visibility_list_opportunities this brief starts from. On the host device Hi, Moose looks the row up, adds its gap evidence to the brief and reads the pages the AI engines cited for it.
referenceUrlsNoOptional: up to 6 page URLs the AI engines cited for this topic, usually the sources of the opportunity row. Hi, Moose reads each page in full and passes it to the brief as a reference source. Works on the host device and in the cloud.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / opportunityId
      Added value: +{
      +  "description": "Optional: the opportunity id from visibility_list_opportunities this brief starts from. On the host device Hi, Moose looks the row up, adds its gap evidence to the brief and reads the pages the AI engines cited for it.",
      +  "maxLength": 300,
      +  "type": "string"
      +}
    • addedInput schema / properties / referenceUrls
      Added value: +{
      +  "description": "Optional: up to 6 page URLs the AI engines cited for this topic, usually the sources of the opportunity row. Hi, Moose reads each page in full and passes it to the brief as a reference source. Works on the host device and in the cloud.",
      +  "items": {
      +    "maxLength": 2000,
      +    "type": "string"
      +  },
      +  "maxItems": 6,
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the agent knows this is a non-idempotent write against live external data. The description adds real value beyond that: a one-to-three-minute latency estimate, the return shape (markdown plus structured fields plus a briefId), and a host-vs-cloud behavior difference for referenceUrls. It does not clarify what is persisted or how to handle repeated calls, so it stops short of fully earning a higher score.

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?

Front-loaded with purpose, then when-to-use, then return values, then the opportunity workflow — a sensible order with no filler sentences. It is slightly long and the opportunityId/referenceUrls reading behavior is stated twice (in the main body and again inside the parameter descriptions), which is mild redundancy rather than waste.

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 seven-parameter, no-output-schema generation tool, the definition covers everything an agent needs: cost/latency, return shape, required vs optional inputs, the specialized opportunity flow, and the instruction to surface the brief verbatim. No output schema is needed because the description states what comes back.

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 genuinely adds meaning beyond the schema by explaining the coupling between opportunityId and referenceUrls — namely that Hi, Moose reads the cited pages and uses them as reference sources — which the schema documents only in isolation. It also explains the downstream use of the returned briefId.

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?

Opens with a specific verb and resource ("Creates a search-informed content brief in Hi, Moose for one project") and immediately enumerates what the brief contains, so the agent knows exactly what artifact it is producing. It also disambiguates from siblings by noting the returned briefId feeds create_draft and that the brief originates from visibility_list_opportunities rows.

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

Usage Guidelines5/5

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

Gives an explicit trigger ("Use it when the user wants a brief for a page or article on their site") plus a concrete alternative path: when starting from a visibility_list_opportunities row, pass that row's opportunityId and source URLs. It also states a downstream rule ("Give the returned brief to the user in full") that removes ambiguity about what to do with the result.

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