Skip to main content
Glama

Add a brand

create_brand
Idempotent

Add a brand (one per product or project) to the Echoly workspace, with manual approval. Returns the brand and a connect_url where the person connects its X, Telegram, Bluesky, Mastodon or Discord accounts. A brand with the same name is returned instead of adding a second one.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe brand's name, usually the product's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world, so the bar is lower; the description still adds real behavior beyond them — a manual approval step, name-based dedupe returning the existing brand instead of erroring, and a connect_url for linking X/Telegram/Bluesky/Mastodon/Discord accounts. It does not say who approves or what the response looks like during pending approval.

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 tight sentences, front-loaded with the action and scope, then return value, then duplicate behavior. The enumerated channel list is slightly heavy but each clause carries information an agent needs.

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?

With no output schema, the description usefully summarizes the return (brand plus connect_url). The only gap for a single-parameter creation tool is the manual-approval mechanics — whether the brand is usable immediately — which is minor but not trivial.

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% and there is only one parameter, so the schema carries the mechanics. The description still adds semantic weight by implying the name is the identity key used for dedupe and by framing it as the product/project name, which matters for correct reuse.

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 ("Add a brand") plus scope ("one per product or project", "to the Echoly workspace"), which cleanly separates it from create_post/list_brands siblings. It also names the return payload, so the agent knows exactly what the call produces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The "one per product or project" phrasing implies when this tool applies, and the dedupe sentence warns that duplicates will not be created. However, it never says to call list_brands first or names any alternative path, so guidance stays implied rather than explicit.

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