Skip to main content
Glama

brand_read

Destructive

Read a brand from its website and its Instagram, TikTok or Facebook accounts, and save it as the brand profile: name, logo, colours, voice, products, audiences, competitors and market white space. Free, takes 1 to 3 minutes. Start it with "url", "socials" or both: a creator or a shop with no website is read from its accounts alone. It answers with a jobId: call this tool again with only "jobId" to follow it (each call waits up to 20 seconds for progress). When status is "done", call brand_profile. Reading again replaces the current profile, so only do it when the user asks or when brand_profile has nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "brand_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoThe brand website, e.g. "hookbird.ai", or a profile link, e.g. "instagram.com/gymshark", to start a read
jobIdNoThe jobId of a read that was started, to get its progress
socialsNoSocial accounts to read, with or without a website

Output Schema

NameRequiredDescriptionDefault
stepNo
errorNo
jobIdNo
labelNo
stepsNo
statusNo
partialNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / socials
      Added value: +{
      +  "description": "Social accounts to read, with or without a website",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "handle": {
      +        "description": "The username, e.g. \"gymshark\", or the profile link",
      +        "type": "string"
      +      },
      +      "network": {
      +        "enum": [
      +          "instagram",
      +          "tiktok",
      +          "facebook"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "network",
      +      "handle"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 6,
      +  "type": "array"
      +}
    • changedInput schema / properties / url / description
      Previous value: -"The brand website, e.g. \"hookbird.ai\", to start a read"New value: +"The brand website, e.g. \"hookbird.ai\", or a profile link, e.g. \"instagram.com/gymshark\", to start a read"
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing cost and duration ("Free, takes 1 to 3 minutes"), the async job pattern with a 20-second wait per call, and the destructive consequence ("Reading again replaces the current profile") which is consistent with destructiveHint=true and idempotentHint=false. The only small gap is that it doesn't say what happens to an in-flight job if started again, but the annotation picture is already covered.

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 the what, then the start/poll/finish workflow, then the caveat — a logical order with no filler sentences. It is dense and slightly long for a single description, but every sentence carries actionable information.

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 an async, multi-mode, destructive mutation tool with an output schema, the description covers initiation, polling cadence, terminal status handling, the required follow-up tool, and the re-run hazard. Nothing an agent needs to invoke it correctly is missing.

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, and the description adds genuinely new semantics: url may be a website or a profile link, url and socials are independently optional and combinable ("a creator or a shop with no website is read from its accounts alone"), and jobId-only calls become polling. It does not explain the socials maxItems of 6 or network enum, but the schema covers those.

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 and resource ("Read a brand from its website and its Instagram, TikTok or Facebook accounts") and names what it produces (the brand profile with name, logo, colours, voice, products, audiences, competitors, market white space). The sibling brand_profile is contrasted implicitly by naming it as the next step, so an agent knows this tool creates/produces the profile while brand_profile reads it.

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?

Explicitly says how to start ("url", "socials" or both), how to poll (call again with only "jobId"), what to do on completion (call brand_profile), and when NOT to run it ("only do it when the user asks or when brand_profile has nothing"). This is a full when/when-not/next-step routing story.

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