Skip to main content
Glama

Rebbel

by io.rebbel
OverviewDiscussionsAdmin

Create brand

create_brand

Creates a new brand — from a website URL (scans the site for logo, colors, copy tone), guided answers (what you sell, who buys it) if there's no site yet, or connectSocialFirst if there's no website at all and the user wants to start from a connected Facebook/Instagram account instead (no site or guided answers needed). First step for a brand that doesn't exist in Rebbel yet. name is optional when websiteUrl or connectSocialFirst is given — Rebbel derives it from the site (or the connected page) and upgrades the guess once the scan/connect completes. Guided (no-website) creation still needs a name. For a website URL, the response includes a real summary of what the scan actually found (name, palette, logo, a voice sample) plus next steps — Rebbel writes the brand's first post's caption on its own: call draft_first_post a few seconds later to fetch it and approve_copy to make its photo (or draft_first_post count: 3-5 for a batch in the site's own voice), or generate_brand_guide for the full brand guide/strategy/ongoing campaigns. connectSocialFirst's response hands off a dashboard connect link instead (Claude can't drive the Meta OAuth dialog itself) — once the user connects, call draft_first_post right away for the same fast batch, or generate_brand_guide once the scan finishes for the full brand guide (check list_connections/list_brands if unsure it's done yet).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe brand/business name. Optional when websiteUrl or connectSocialFirst is given — Rebbel derives it from the site (or the connected page) and upgrades the guess once the website scan/connect completes. Required for guided (no-website) creation.
guidedNoOnly when there's no website: what the brand sells, who buys it, and any existing assets/colors/tagline to carry over.
websiteUrlNoThe brand's website, if it has one — triggers a scrape of the real site (logo, colors, copy tone). A bare domain like 'example.com' is fine, the scheme is added automatically.
connectSocialFirstNoSet true instead of websiteUrl/guided when the user wants to connect a social account first and skip straight to a first post — the fastest path for a brand-new user. No website scan runs; the tool response includes a dashboard link to connect. Once connected, call draft_first_post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / guided / properties / identityKind
      Added value: +{
+  "description": "\"business\" (default) or \"person\" when the brand is the owner themselves and their work (an agent, a musician, a solo practice).",
+  "enum": [
+    "business",
+    "person"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / guided / properties / profileUrl
      Added value: +{
+  "description": "Optional: one link people use to find them (Linktree, an artist or agent page, a social profile). Public pages are read once for words and photos; Instagram, Facebook, TikTok, X, LinkedIn and Threads links are never read, only offered as channels to connect.",
+  "format": "uri",
+  "type": "string"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safety profile (non-read-only, non-destructive, open-world, non-idempotent); the description adds substantially more: the scan is asynchronous and the derived name is upgraded once it completes, the response contains a real scan summary plus next steps, and connectSocialFirst returns a dashboard link because Claude cannot drive the Meta OAuth dialog. That last point is a genuine capability boundary an agent would otherwise discover only by failure.

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 and the mode decision, and every clause carries operational information (which mode, what the response contains, what to call next). It is a single dense paragraph with several very long clauses, so it is heavier to parse than it needs to be, but almost nothing is filler.

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?

There is no output schema, so the description correctly compensates by describing what each mode returns (scan summary with name/palette/logo/voice sample, or a dashboard connect link) and what must happen next. For a multi-mode, async, chained-write tool with a nested guided object, this covers everything an agent needs to invoke and sequence it.

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, but the description adds cross-parameter meaning the schema states only per-field: that name is optional specifically when websiteUrl or connectSocialFirst is given and required for guided creation, and that connectSocialFirst is an alternative to both websiteUrl and guided rather than a complement. It does not add syntax detail beyond that, keeping it at 4.

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 (creates a new brand in Rebbel) and immediately enumerates the three mutually exclusive creation modes (websiteUrl scan, guided answers, connectSocialFirst). It also explicitly positions itself as 'First step for a brand that doesn't exist in Rebbel yet', which separates it from rename_brand/archive_brand and from the downstream generate_* siblings.

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?

Explicit routing rules for every branch: use guided only when there's no website, use connectSocialFirst only when there's no site at all and the user wants to start from a connected Facebook/Instagram account. It also names the exact follow-up tools per branch (draft_first_post, approve_copy, generate_brand_guide, list_connections/list_brands) and when to call each.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Rebbel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources