Skip to main content
Glama
Sign In

Google Sheets MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Google Sheets Execute Action

execute_action
Destructive

Execute Google Sheets action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, spreadsheet_id, sheet_id AND available_requests

  2. request='actions_details' with actions=['query_sheet_data'] - Get detailed body structure

Common actions: query_sheet_data (read/filter data), update_cells (write), get_sheet_peak (preview), add_rows, create_spreadsheet.

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, and the description is consistent with that by flagging update_cells as a write. It adds the workflow dependency and the 'follow the schema exactly' constraint, but gives no detail on what update_cells/add_rows may overwrite, whether operations are reversible, or any rate/targeting limits.

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?

Numbered prerequisite steps and a compact action list are front-loaded and scannable. A little redundancy exists between 'Rely on info from steps 1-2' and the REQUIRED block, but nothing is wasted.

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?

An output schema exists, so return values need no explanation, and the description covers the essential prerequisites and the range of actions available. The remaining gap is the opaque body contract, which is mitigated by pointing to the discovery step rather than left unaddressed.

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?

The single `body` parameter is an untyped object with additionalProperties=true and 0% schema description coverage, so the schema provides essentially nothing. The description compensates procedurally by telling the agent to fetch the body structure via query_contexts request='actions_details', which is genuinely useful, but it does not describe the body shape itself.

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 ('Execute Google Sheets action') and enumerates concrete action types (query_sheet_data, update_cells, add_rows, create_spreadsheet), which makes the tool's scope tangible. It clearly positions itself as the terminal step of a workflow, distinguishing it from the sibling query_contexts, though the generic name 'execute_action' is only disambiguated by the body text.

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?

Explicitly requires two prior query_contexts calls with exact request values ('accounts', 'actions_details' with actions=['query_sheet_data']) before invocation, and names the sibling tool to use. It does not state any when-not-to-use or exclusion conditions, which keeps it 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 Google Sheets 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