Skip to main content
Glama

brand_profile

Read-onlyIdempotent

Get the brand Hookbird knows for this account: name, website, niche, voice, products, positioning, competitors and audiences (each audience has an id, what they want and what they are stuck on). "kind" says whether it is a brand or a creator (one person; their audiences are viewers). "socials" are the Instagram, TikTok and Facebook accounts it read, and "whatWorks" their posts that beat the account's usual (lift = times its median), with why and the hook as a reusable pattern. Call this first in any content task: hooks, angles, plans and Studio content are all written from it. Pass an audience id to hooks_generate, hooks_score and strategy_plan to aim at one audience. When "found" is false the brand was never read: ask for the website or the Instagram or TikTok account and call brand_read.

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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNo
foundYes
profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description adds the important empty-state behavior ("found" false means the brand was never read) and explains derived semantics such as lift being a multiple of the account's median and whatWorks being an extractable reusable pattern. It does not discuss freshness of the cached brand data or what happens for multi-account contexts, which keeps it below a 5.

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?

Three short blocks: return contents, semantics of special fields, then call-order and failure handling. It is dense but every sentence carries information. The main cost is that the highest-value instruction ("call this first") sits in the third block rather than being front-loaded.

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?

The tool is a parameterless read with an output schema, so the description only needed to cover call ordering, field semantics and the empty state — and it covers all three, including the exact remediation for a miss. Nothing an agent needs to select or 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?

Zero parameters, so there is nothing to disambiguate and the baseline is 4. The description does useful adjacent work by telling the agent where the audience id it returns should be passed (hooks_generate, hooks_score, strategy_plan), effectively documenting the handoff rather than a param.

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 ("Get the brand Hookbird knows for this account") and then enumerates the exact fields returned: name, website, niche, voice, products, positioning, competitors, audiences. It also distinguishes the entity types via "kind" (brand vs. creator) and clarifies what "socials" and "whatWorks" mean, so an agent knows precisely what this tool yields 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 Guidelines5/5

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

Gives an explicit priority rule ("Call this first in any content task: hooks, angles, plans and Studio content are all written from it") and names the downstream consumers (hooks_generate, hooks_score, strategy_plan) plus how to use the audience id with them. It also names the fallback path: when "found" is false, ask for the website or Instagram/TikTok account and call brand_read.

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