StealAds

Update a brand

update_brand

Idempotent

Changes one brand's name, industry, website, primary color, tone of voice or target audience and returns the updated brand; fields left out stay as they are, and at least one is needed. Product details, offers, writing rules and other brand settings are not editable here; those are changed in the StealAds web app. Does not read the website, re-run brand discovery or spend credits.

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

Input Schema

Name	Required	Description
`name`	No	New brand name, up to 200 characters.
`brand_id`	Yes	Brand id from list_brands.
`industry`	No	Industry or category the brand sells in, in plain words.
`websiteUrl`	No	Brand website as a full URL. Stored only; the site is not read or crawled.
`toneOfVoice`	No	How the brand should sound in ad copy.
`primaryColor`	No	Primary brand color as a six-digit hex value, such as #336699.
`targetAudience`	No	People the brand wants to reach and their needs.

Output Schema

Name	Required	Description	Default
`brand`	No	Accessible brand details.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 10, 2026

changedInput schema / properties / brand_id / description

Previous value: -"Brand reference from list_brands (e.g. the returned brand id)."New value: +"Brand id from list_brands."

changedInput schema / properties / industry / description

Previous value: -"Industry the brand operates in."New value: +"Industry or category the brand sells in, in plain words."

changedInput schema / properties / name / description

Previous value: -"Name of this brand or collection."New value: +"New brand name, up to 200 characters."

changedInput schema / properties / websiteUrl / description

Previous value: -"Brand website URL; supplying it does not crawl the site."New value: +"Brand website as a full URL. Stored only; the site is not read or crawled."

First observedNov 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations, the description discloses partial-update behavior, the return value, and important non-effects: it does not read the website, re-run brand discovery, or spend credits. These are meaningful behavioral traits for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and editable fields, then adds constraints and exclusions in compact sentences. No sentence is redundant.

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 a non-destructive, idempotent mutation with full schema coverage and an output schema, the description covers requirements, partial-update behavior, scope exclusions, and side effects. Nothing important for calling it correctly appears 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 already 100%, so the schema carries most parameter detail. The description adds important semantics not enforced by the schema: at least one editable field is required and omitted fields remain unchanged.

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?

The description states a specific verb ('Changes') and resource ('one brand'), enumerates the editable fields, and clarifies that it returns the updated brand. It distinguishes this tool from sibling update tools by explicitly excluding product details, offers, writing rules, and other brand settings.

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?

It gives a clear precondition ('at least one is needed') and explicit partial-update semantics ('fields left out stay as they are'). It also says where non-editable settings must be changed ('the StealAds web app') and rules out discovery-related actions.

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

All StealAds tools Inspect

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.