Skip to main content
Glama

create_persona_brief

create_persona_brief

Generate an AI persona and brand voice brief from the pages of a website (free tool)

Reads public pages of a website and produces an editorial persona and writing style brief: who writes, for whom, tone on 6 axes, vocabulary, structure, do and don't lists, verified quotes from the pages, style metrics measured on the text, and a ready-to-paste writing prompt for any AI writing tool (brief.writingPrompt, plus brief.writingPromptCompact of at most 1500 characters).

Asynchronous, poll the result. This call only starts the job and answers HTTP 202 with a briefId and a pollUrl. Call GET /api/v1/tools/persona-brief?briefId=... every 3 seconds until status is done or failed. A brief takes about 80 seconds plus 5 seconds per page, rounded up to the half minute: about 2 min for 3 pages, 2 min 30 s for 10 pages. MCP clients must call the get_persona_brief tool again until the status is terminal.

Identical requests are reused for 72 hours. The same set of URLs, in any order, with the same outputLanguage and the same brandName, returns the brief already computed instead of computing it again: HTTP 200 with reused true, status already done, the original briefId and reusedCreatedAt, the date of the brief it reuses. Nothing is created, and your daily quota is given back, so a reused answer costs you nothing. The pages of a reused brief are listed in the order of the original request, not in the order you just sent. Send force true to skip the lookup and compute a new brief, which answers 202 and consumes quota.

Addresses. Duplicate URLs, compared once normalized, are read once. A private, local or blocked address is not refused by this call: the brief is created, and that page ends with status failed and failureReason BLOCKED_ADDRESS (the brief fails with NO_USABLE_PAGE when no other page could be read).

Tiers, per UTC day. Every tier is capped at 10 URLs per brief since 21 September 2026.

  • Without an API key, free anonymous tier: 3 briefs per day per IP address, 10 URLs per brief.

  • Signed-in account on the web interface, plan without API access: 10 briefs per day, 10 URLs per brief.

  • API key of an account whose plan includes API access, pro tier: 50 briefs per day, 10 URLs per brief.

The API key of an account whose plan does NOT include API access does not authenticate, and the call returns 401. Remove the Authorization header to use the free anonymous tier instead.

Quota headers: X-RateLimit-Limit, X-RateLimit-Used, X-RateLimit-Remaining, X-RateLimit-Reset (Unix time of the next UTC midnight). Retry-After is set on 429 and 503. A 502 or 503 answer gives the consumed quota back, and so does a 429 FREE_CAPACITY_REACHED and a 200 reused answer; SERVICE_UNAVAILABLE consumes none.

Request format. Send the body as JSON with Content-Type: application/json: any other content type returns 415. Without an Authorization header, a request sent by a web page of another site (an Origin other than the SERPmantics app, or Sec-Fetch-Site: cross-site) returns 403. Server-to-server calls send no Origin header and are not affected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesPublic http(s) URLs of representative pages of one website, 5 to 10 articles give the best brief. At most 10 URLs, whatever the tier, each of at most 2048 characters.
forceNoTrue to compute a new brief even when an identical one exists, which answers 202 and consumes quota. Any value that is not a boolean returns 400 INVALID_BODY.
brandNameNoOptional brand name, on a single line, used in the brief.
outputLanguageNoLanguage in which the brief is written. When omitted, the service chooses it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / force
      Added value: +{
      +  "description": "True to compute a new brief even when an identical one exists, which answers 202 and consumes quota. Any value that is not a boolean returns 400 INVALID_BODY.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / urls / description
      Previous value: -"Public http(s) URLs of representative pages of one website, 5 to 10 articles give the best brief. At most 10, 20 or 30 URLs depending on the tier, each of at most 2048 characters."New value: +"Public http(s) URLs of representative pages of one website, 5 to 10 articles give the best brief. At most 10 URLs, whatever the tier, each of at most 2048 characters."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully carries the burden, and it does so exhaustively: it discloses async behavior (202 + pollUrl), reuse caching (72h, order-insensitive, reusedCreatedAt), address handling (blocked/local, BLOCKED_ADDRESS, NO_USABLE_PAGE), tier limits, quota headers, error codes (401, 403, 415, 429, 502, 503), and auth requirements (Origin checks). Nothing is hidden.

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

Conciseness5/5

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

Despite being long, the description is tightly organized with bolded section headers (Asynchronous, Identical requests, Addresses, Tiers, Request format) that let an agent scan quickly. Every sentence carries operational value—no fluff. The core purpose is front-loaded, and the rest is structured detail an agent actually needs.

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 complex async tool with quotas, reuse, and error handling, the description covers all necessary operational aspects: polling procedure, reuse semantics, address behavior, tier limits, quota headers, and request format constraints. With no output schema, it also describes what the brief contains and where to find the writingPrompt. An agent has everything required to call it correctly and interpret results.

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. The description adds meaningful context beyond the schema: it explains that outputLanguage and brandName are part of the reuse key, that force skips the reuse lookup and consumes quota, and that urls are normalized and deduplicated. This extra behavioral linkage enhances understanding of each parameter.

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 opens with a specific verb and resource: 'Generate an AI persona and brand voice brief from the pages of a website.' It immediately distinguishes this from sibling creation tools by focusing on persona briefs, and it clarifies the scope (public pages) and output (writing style brief). No ambiguity about what it does.

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?

The description gives explicit usage instructions: it is asynchronous, so clients must poll via get_persona_brief until terminal status; it explains reuse and force; and it details tiers and quotas. However, it does not explicitly compare against alternatives like create_eeat or discover_persona_brief_pages, so the 'when vs alternatives' guidance is implied rather than stated. Clear context and exclusions for the async flow are provided, so a 4 is warranted.

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