Skip to main content
Glama

Execute Pica Action

execute_pica_action

Execute actions on third-party platforms to read, create, update, or delete data, such as fetching contacts or creating tasks.

Instructions

Execute a Pica action to perform actual operations on third-party platforms. CRITICAL: Only call this when the user's intent is to EXECUTE an action (e.g., 'read my last Gmail email', 'fetch 5 contacts from HubSpot', 'create a task in Asana'). DO NOT call this when the user wants to BUILD or CREATE code/forms/applications - in those cases, stop after get_pica_action_knowledge and provide implementation guidance instead. REQUIRED WORKFLOW: Must call get_pica_action_knowledge first. If uncertain about execution intent or parameters, ask for confirmation before proceeding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesPlatform name
actionYesAction object with ID, path, and method
connectionKeyYesKey of the connection to use
dataNoRequest data (for POST, PUT, etc.)
pathVariablesNoVariables to replace in the path
queryParamsNoQuery parameters
headersNoAdditional headers
isFormDataNoWhether to send data as multipart/form-data
isFormUrlEncodedNoWhether to send data as application/x-www-form-urlencoded
Behavior4/5

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

No annotations provided, so description carries the burden. It discloses critical behavioral constraints: only execute when user intends to execute, not for building. It mentions workflow and caution. However, it lacks details on success/error responses, rate limits, or side effects.

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?

The description is concise (3 sentences) and front-loaded with purpose, followed by critical guidance and workflow. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 parameters, nested objects), no output schema, and no annotations, the description covers when to use but lacks detail on parameter usage, expected output format, and error handling, leaving some gaps.

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 has 100% description coverage, so baseline is 3. The description does not add significant parameter-specific details beyond the schema; it focuses on tool usage rather than parameter meanings.

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 clearly states the tool's purpose: 'Execute a Pica action to perform actual operations on third-party platforms.' It further distinguishes from sibling tools by specifying the required workflow and contrasting with build/create scenarios.

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?

Explicit guidance on when to call (user intent to execute) and when not to call (user wants to build/create). Includes required workflow: must call get_pica_action_knowledge first, and ask for confirmation if uncertain.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcp-research/picahq__mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server