Skip to main content
Glama
Sign In

Shopify MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Shopify Execute Action

execute_action
Destructive

Execute Shopify action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.

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": {
      "body": "<body>"
    },
    "name": "execute_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark the tool as non-read-only, open-world, and destructive. The description adds valuable workflow context that the body must be constructed from prior query_contexts calls and that this is the final execution step, but it does not elaborate on irreversible side effects or failure behavior beyond what annotations imply.

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 tool's purpose and workflow position, followed by numbered required steps. Every sentence serves the workflow, though there is some redundancy between listing step 2 and separately emphasizing 'Always call step 2'.

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?

Given the dynamic action body, destructive/open-world annotations, and existing output schema, the description provides the essential prerequisite workflow and body-construction guidance. It omits explicit warnings about destructive effects, but annotations cover that safety profile and return values are covered by the output schema.

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 description coverage is 0% for the single free-form 'body' object, so the description must compensate. It does so by instructing the agent to obtain the exact body structure via query_contexts 'actions_details' and to follow the schema exactly, which is the key semantic guidance for a dynamic action body.

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 clearly states the tool executes a Shopify action and positions it as Step 3 (FINAL) of a workflow. It distinguishes itself from query_contexts by requiring that tool for prerequisite data, though it does not describe what kinds of actions are available beyond referencing available_actions.

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 explicit mandatory prerequisites: call query_contexts with request='accounts' and then request='actions_details' before executing. It also names the alternative tool for each step and states 'Always call step 2' before execution, leaving little ambiguity about when and how to use this tool.

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

All Shopify MCP by InsightfulPipe 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