Skip to main content
Glama

Plunder & Riffle Meme Engine

Research a brand's voice

research_brand
Read-only

Deep-dive ONE client's business from url or notes → brandProfile {name, voice, hashtag, token} + analysisSummary (the /admin persona engine). Free. If their site blocks the scraper, free DuckDuckGo (then Exa) snippets stand in — evidenceVia says which. One page: a voice, not a market study; never invents a price or a result. brief: true adds campaign — offer, audience, pains, objections, proof, angles, each a verbatim quote or unknown. Then save_brand_default or create_campaign_from_research.

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": "research_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoTheir website, http(s), ≤300 chars.
briefNoAlso return the sourced CampaignResearch brief (`campaign`).
notesNoWhat they sell and to whom, when there's no readable site. ≤2000 chars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds substantial behavior: it is free, it degrades to search snippets, evidenceVia discloses which source was used, and it never invents a price or result. It also explains the extra campaign payload structure and that its fields are verbatim quotes or 'unknown'.

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 core action and outputs, then fallbacks and follow-ups. Arrow notation and field braces keep it tight. A few dense fragments ('the /admin persona engine') slightly reduce readability for an outside agent.

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?

With no output schema, the description carries the full burden and does: it enumerates brandProfile fields, analysisSummary, evidenceVia, and the campaign subfields. Fallback sourcing and the no-fabrication guarantee cover the remaining behavioral questions an agent would have.

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 baseline is 3, and the description still adds meaning: url versus notes is framed as 'when there's no readable site,' and brief:true is expanded into the specific campaign fields returned. The added context is real but mostly covered by the schema's own descriptions.

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 (deep-dive ONE client's business) and names the concrete outputs (brandProfile with name, voice, hashtag, token, plus analysisSummary). The 'ONE client / a voice, not a market study' framing separates it cleanly from bulk or market-research siblings.

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 sourcing logic (url or notes; DuckDuckGo then Exa fallback when the site blocks the scraper) and explicit follow-on actions (save_brand_default or create_campaign_from_research). It stops short of stating when to prefer a different research tool, but the 'voice, not a market study' line implicitly excludes broader analyses.

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