WisePPC

get_mutations

Read-onlyIdempotent

Status of submit_mutation changes: pending, executed, failed, or canceled, with phase, reason, and reviewer thread. mutationId returns one change in full, or byte slices with next_cursor; no id returns a compact list (visible rows; mineOnly=true: the caller's); waitSeconds long-polls until one changes (max 55; {event:'timeout'} is an empty wait). source=legacy is read-only history.

Input Schema

Name	Required	Description	Default
`limit`	No	Default 50, max 500.
`since`	No	ISO-8601; source=legacy only.
`cursor`	No	queue page or record slice: pass the previous next_cursor; omit on the first page
`offset`	No	source=legacy only.
`source`	No		all
`status`	No
`batchId`	No	List one batch.
`verbose`	No
`mineOnly`	No
`profileId`	No	Amazon advertising profile ID.
`mutationId`	No	One mutation's UUID.
`mutationIds`	No	waitSeconds: only these.
`waitSeconds`	No	Long-poll seconds (default 50). Needs profileId.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / businessProfileId

Removed value: -{
-  "description": "Business profile ID.",
-  "type": [
-    "integer",
-    "string"
-  ]
-}

Changed2 schema fields changedOct 29, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "queue page or record slice: pass the previous next_cursor; omit on the first page",
+  "type": "string"
+}

addedInput schema / properties / offset / description
```
Added value: +"source=legacy only."
```

First observedOct 18, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses pagination via `next_cursor`, byte-slice behavior, compact-list behavior, long-poll limits, timeout semantics, and legacy read-only history. These operational details materially help an agent understand how the call behaves.

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?

The description is compact and front-loads the core purpose, with no wasted sentences. However, it is a dense semicolon-heavy block, which reduces readability despite being concise.

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 13-parameter query tool with no output schema, the description covers the main retrieval modes, return-style distinctions, pagination, long-poll behavior, and legacy-source constraints. It is largely complete, though it leaves some filter and output-detail gaps for the schema and agent inference.

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?

With 69% schema coverage, the description adds important meaning for `mutationId`, `cursor`, `mineOnly`, `waitSeconds`, and `source=legacy` that the schema alone only partially conveys. It does not explain every filter such as `batchId`, `verbose`, or `status` values, so the schema still carries some weight.

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-resource pair, mutation status, and immediately names the sibling action it reports on (`submit_mutation`). It also distinguishes the main retrieval modes: single mutation, list, byte slices, long-poll, and legacy history.

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?

It gives clear mode-selection guidance: `mutationId` for one change, no id for a compact list, `mineOnly=true` for the caller's rows, `waitSeconds` for long-polling, and `source=legacy` for read-only history. It does not explicitly name alternatives such as `get_events` or state when not to use this tool, so it stops short of a 5.

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

All WisePPC 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.

Resources

Need Help?