Vendooly

log_action

Record one operation done on ONE outpost (seller × marketplace) in the Vendooly action log, so it is remembered and its impact on the KPI can be measured later. Owners/admins only. Call it right AFTER a write that succeeded (Ads, price, listing, stock) or after a manual change the user reports, with the value before → after. Internal Vendooly log: writes nothing on Amazon.

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": {
      "outpost_id": "<outpost_id>",
      "kpi": "<kpi>",
      "action_type": "<action_type>",
      "description": "<description>"
    },
    "name": "log_action"
  }
}

Input Schema

Name	Required	Description
`kpi`	Yes	KPI the operation is meant to move.
`ref`	No	Optional: campaign/keyword/SKU/ASIN id or a link.
`actor_ref`	No	Optional: name of the person/agent/session.
`actor_type`	No	Who did it (default user).
`outpost_id`	Yes	Id outpost (seller × marketplace).
`action_type`	Yes	Short code, e.g. bid_change, budget_change, price_change, negative_keyword, listing_fix (max 60 chars).
`description`	Yes	What was done, in one sentence (max 500 chars).
`value_after`	No	Valore dopo l'azione.
`value_before`	No	Valore prima dell'azione.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 9, 2026
- addedInput schema / properties / outpost_id / description
```
Added value: +"Id outpost (seller × marketplace)."
```
- addedInput schema / properties / value_after / description
```
Added value: +"Valore dopo l'azione."
```
- addedInput schema / properties / value_before / description
```
Added value: +"Valore prima dell'azione."
```
AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the bar is lower, but the description still adds real context: owners/admins only, and that the write is confined to an internal Vendooly log with nothing sent to Amazon. It does not address duplicate handling or repeated logging, which would have made this 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.

Conciseness5/5

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

Three tight sentences: purpose first, permissions and scope second, invocation timing third. Nothing is repeated from the schema and no sentence is filler.

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 nine parameters, no output schema and a mutation annotation profile, the description covers the essential gaps: permissions, internal-only scope, and post-write timing. It stops short of stating whether repeated identical entries are accepted or deduplicated, which is the only notable omission.

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 the baseline is 3; the description still adds meaning by tying value_before and value_after to the required 'before → after' convention and by framing the outpost as seller × marketplace. Remaining parameters such as ref and actor_ref are left entirely to the schema.

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 and resource: record one operation on ONE outpost (seller × marketplace) in the Vendooly action log. The explicit 'ONE outpost' scope and named log distinguish it cleanly from the sibling list_action_log, which reads that log rather than writing to it.

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 an explicit trigger and timing: call it right AFTER a successful write (Ads, price, listing, stock) or after a manual change the user reports. It also states the payload convention (value before → after), so the agent knows both when and how to invoke it.

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

All Vendooly 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?