Skip to main content
Glama
Sign In

Gloriads — Amazon Ads

by com.gloriads
OverviewDiscussionsAdmin

What Gloriads did on Amazon

list_activity
Read-onlyIdempotent

List every operation Gloriads ran on the Amazon Ads account, newest first: campaigns created or copied, products added, templates applied, a rule's changes (one operation per marketplace, more past 5,000 lines, sharing a rule_run_id), dayparting changes, a change past 5,000 lines from any tool coming in parts (each later part naming the first in part_of), structure corrections and undos, each with its marketplace, status and how many lines succeeded, failed or were skipped. Paginated: follow next_cursor while has_more is true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoKeep only one tool's operations.
limitNoItems per page, 1 to 100. Defaults to 50.
cursorNoThe `next_cursor` of the previous page, to read the next one. Treat it as opaque.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tool / enum
      Previous value: -[
-  "addProducts",
-  "duplicateCampaign",
-  "applyTemplate",
-  "bulkLaunch",
-  "addNegatives",
-  "renameCampaigns",
-  "createCampaign",
-  "createSbCampaign",
-  "createSdCampaign",
-  "createStCampaign",
-  "rule",
-  "cleanStructure",
-  "stateSwitch",
-  "budgetCap",
-  "bulkEdit",
-  "bidLimits",
-  "asinSwitch",
-  "addKeywords",
-  "addTargets",
-  "dayparting",
-  "undo"
-]New value: +[
+  "addProducts",
+  "duplicateCampaign",
+  "applyTemplate",
+  "bulkLaunch",
+  "addNegatives",
+  "renameCampaigns",
+  "createCampaign",
+  "createSbCampaign",
+  "createSdCampaign",
+  "createStCampaign",
+  "rule",
+  "cleanStructure",
+  "stateSwitch",
+  "budgetCap",
+  "bulkEdit",
+  "bidLimits",
+  "asinSwitch",
+  "addKeywords",
+  "addTargets",
+  "dayparting",
+  "offAmazonReach",
+  "undo"
+]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. Beyond that, the description adds meaningful behavior: results are newest first, rule changes may be split across marketplaces and lines, oversized changes may arrive in parts linked by rule_run_id and part_of, and each entry includes marketplace, status, and success/failure/skip counts. It does not cover auth requirements or rate limits, but it provides substantial context for a read tool.

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 front-loaded with the core purpose and then elaborates on operation types, grouping behavior, and pagination. It is dense and runs as a long sentence, which makes it slightly harder to scan, but nearly every detail earns its place.

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 read-only listing tool with no output schema, the description covers ordering, pagination, operation types, grouping semantics, and per-entry fields well enough for an agent to call it correctly. The main remaining gap is explicit sibling differentiation, since get_activity and list_activity_lines are not addressed.

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 description coverage is 100%, and all three parameters are documented in the input schema, including the tool enum, limit bounds, and cursor opacity. The description reinforces pagination behavior with next_cursor and has_more but does not add parameter-specific meaning beyond the schema. The high schema coverage makes 3 the appropriate baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: listing every operation Gloriads ran on the Amazon Ads account, ordered newest first. It enumerates the operation types covered, so an agent can understand the scope. It does not explicitly distinguish this tool from close siblings like get_activity, get_timeline, or list_activity_lines.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The pagination guidance is clear: follow next_cursor while has_more is true. However, there is no explicit guidance on when to use this tool instead of siblings such as get_activity or list_activity_lines, nor any stated exclusions. Usage is therefore implied rather than fully specified.

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

All Gloriads — Amazon Ads 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