Skip to main content
Glama

Add or edit a listing option

optimizer_save_option

Add or replace a listing option to re-score it and flag validation issues; text differing from live becomes the Copy draft, ready to publish.

Instructions

Add your own listing option (omit optionId) or replace the listing of an existing option. The app re-scores it and reports validation problems (length limits, repeated words) in get_optimizer. A description or promotional text you set on the chosen option (or on an option you then choose) that differs from the live text becomes the Copy draft with publishing switched on, so publish_listing sends it.

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": {
      "projectId": "<projectId>",
      "listing": "<listing>"
    },
    "name": "optimizer_save_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoName for a new option.
listingYes
optionIdNoOption to replace; omit to add a new one.
projectIdYesProject id (from get_overview).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare the generic write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description goes further by disclosing two non-obvious side effects: the option is re-scored with validation errors routed to get_optimizer, and any differing description/promotionalText silently becomes the Copy draft with publishing switched on while remaining unsent until publish_listing. The second sentence is dense enough that the exact draft/live state takes re-reading, which keeps this from 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.

Conciseness3/5

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

The add/replace distinction is correctly front-loaded, but the second sentence crams draft creation, publish-state behavior, and a downstream tool reference into one convoluted clause with a parenthetical detour. No sentence is pure filler, but the packaging costs readability for a rule the agent must not misread.

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?

For a nested-object mutation with no output schema and no annotations covering side effects, the description does real work: it explains scoring, where validation errors appear, and the draft/publish consequence. The main gap is replace semantics — 'replace the listing of an existing option' leaves unclear whether unspecified listing fields are wiped, which matters for a full-overwrite call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75% and the schema already documents optionId as 'Option to replace; omit to add a new one', so the description's add-vs-replace framing largely restates structured data. It adds no field-level guidance for the nested listing object (e.g., whether omitted fields are cleared on replace), which is exactly the semantics an agent would need.

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 and immediately splits the two modes: add a new option by omitting optionId, or replace an existing option's listing. The condition that selects each mode is given inline, so an agent can distinguish it from siblings like optimizer_remove_option or optimizer_edit_locale 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 Guidelines4/5

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

Gives a clear operative rule (omit optionId to add) and situates the tool in a workflow: results are re-scored and validation problems surface via get_optimizer, and the Copy draft is delivered by publish_listing. It does not state when NOT to use it (e.g., versus optimizer_remove_option or optimizer_edit_locale), so it stops short of full alternative routing.

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

Deploy Server

Other Tools