Skip to main content
Glama

Get brief

get_brief
Read-only

Get a brief's status and, once completed, its guidance and assets. Set wait to true to wait until it completes or fails, up to the timeout. If the result is still pending or processing, repeat the same call with wait: true. After the JSON, each image asset has a resource link to the same URL, followed by the image when it fits the size limit. Only the brief's creator can read it.

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": {
      "brief_id": "<brief_id>"
    },
    "name": "get_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait while the brief is pending or processing, until it completes or fails or the timeout expires. Defaults to false.
timeoutNoHow long this read may wait, in seconds, including setup and polling. Applies when wait is true. Defaults to and is capped at 45 seconds.
brief_idYesID of the Brief whose status, guidance, and assets to retrieve. Use brief_id returned by create_brief.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
inline_mediaNoSet to false to get only the JSON and resource links, without images or audio, for example when re-reading a result you have already seen. Defaults to true, which adds images and audio after their links while the result stays within its size limit.

Output Schema

NameRequiredDescriptionDefault
errorNoFailure details. Present once the brief failed.
assetsNoBrand files selected for the task. Present once the brief completes.
statusYesCurrent brief status.
brief_idYesBrief ID. Once the brief is completed, pass it as brief_id to generate_image or generate_video.
guidanceNoBrand guidance for the task. Present once the brief completes.
skill_idYesID of the Brand Skill version the brief used, or null once that version is deleted.
failed_atNoTime the brief failed. Present once failed.
created_atYesTime the brief was created.
completed_atNoTime the brief completed. Present once completed.
message_for_assistantNoContext, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real context beyond them: creator-only authorization, bounded blocking via timeout, the polling pattern, and the response layout (JSON first, then resource links, then inline images within a size limit). The idempotentHint=false is consistent with the described repeat-with-wait pattern. Rate limits are not mentioned, but coverage is strong.

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 behavior, then permissions; no filler sentences. Slightly dense with the linking/image rendering detail, but every sentence describes behavior an agent needs to interpret the response.

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?

An output schema exists, so return-value documentation is not strictly required, yet the description still explains response ordering and the pending/processing states. With annotations covering the safety profile and full schema coverage, an agent has what it needs to call this correctly; the only omission is how 'fails' results surface.

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 meaning: it explains that waiting is bounded 'up to the timeout', and that images/audio appear after their resource links only while the result fits a size limit — useful framing for deciding whether to pass inline_media. llm_model is left entirely to 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?

States a specific verb+resource: it returns a brief's status and, once completed, its guidance and assets. The 'brief' resource is clearly distinct from the sibling generation/review/brand resources, so an agent can route 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?

Gives clear operational guidance: set wait to true to block until completion/failure, and repeat the same call with wait:true if still pending. It also states the creator-only access prerequisite. It does not explicitly contrast with sibling readers (e.g., get_generation), but the when-to-use guidance for the wait/poll loop is concrete.

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