Skip to main content
Glama
Sign In

Jepto

by com.jepto
OverviewDiscussionsAdmin

Actions Execute

actions_execute
Destructive

Runs a marketing platform action for a client. The first call returns a preview and executionId; the action runs only after the user confirms in the app, and can be cancelled instead. actionId and the inputs schema come from the actions_list catalog.

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": {
      "clientId": "<clientId>",
      "inputs": "<inputs>",
      "reason": "<reason>"
    },
    "name": "actions_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYesAction-specific inputs matching the schema from actions_list. Entity IDs are arrays.
reasonYesShort summary of why the action is being taken.
actionIdNoAction identifier from actions_list response
clientIdYes16-character hex client id, as returned by client_list.
cancelledNoSet to true to cancel a pending execution. Default: false.
confirmedNoSet to true only when re-calling after user has confirmed. Default: false.
executionIdNoUUID v7 string from the confirmation response. Empty on first call; required when confirmed=true or cancelled=true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description goes beyond them by disclosing the two-phase confirm/cancel protocol, so the agent knows a call alone does not execute the action and that executionId threading is required. Minor gaps remain on failure behavior and permission requirements.

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?

Two dense sentences with zero filler; the execution model and the confirmation gate are front-loaded before the parameter sourcing note.

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 destructive, nested-input, 7-parameter write tool with no output schema, the description covers the essential protocol (preview, confirm, cancel) and names where to source actionId and inputs. It stops short of describing error cases or what the preview contains, which an agent would need for edge handling.

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, but the description adds a cross-tool fact the schema cannot convey: actionId and the inputs schema originate from the actions_list catalog. The confirmation/executionId semantics are left to the schema, which documents them adequately.

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?

States a specific verb and resource ('Runs a marketing platform action for a client') and ties actionId/inputs to the actions_list catalog, which implicitly separates it from the catalog browsing sibling. It doesn't explicitly say 'use actions_list to discover actions, then call this to execute', so the differentiation is inferential rather than stated.

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 clear operational context: the first call returns a preview and executionId, and the action only runs after user confirmation in the app, with cancellation as an option. This is real when/how guidance, though it doesn't state exclusions such as what conditions make an action ineligible to run.

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

All Jepto 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