mcp-magento-cloud

get_activity_log

Retrieve the log output for a specific activity on a Magento Cloud environment, or the most recent activity if no ID is provided.

Instructions

Display the log output for a specific activity on a Magento Cloud environment. If no activity ID is provided, shows the log for the most recent activity.

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": {
      "project": "<project>",
      "environment": "<environment>"
    },
    "name": "get_activity_log"
  }
}

Input Schema

Name	Required	Description
`id`	No	The activity ID. Defaults to the most recent activity if omitted. Use list_activities to find IDs.
`project`	Yes	The Magento Cloud project ID
`environment`	Yes	The environment name, e.g. 'staging', 'production'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.0Jul 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations provided, so the description carries the burden. It discloses that the tool defaults to the most recent activity if no ID is given. The operation is clearly read-only and non-destructive, though not explicitly stated.

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 highly concise, consisting of two sentences with no extraneous information. It front-loads the main purpose and efficiently covers the default behavior.

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 simple retrieval tool with no output schema, the description adequately explains the core functionality and default. It could be improved by briefly noting the output format, but overall it is sufficient for an agent to understand and use the tool.

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 baseline is 3. The description adds value by explaining the default behavior for the 'id' parameter when omitted. This provides context beyond the schema descriptions.

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 displays log output for a specific activity on a Magento Cloud environment. It specifies the verb 'Display' and the resource 'log output for a specific activity', and distinguishes from sibling tools like 'list_activities' which provide activity IDs, not logs.

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?

The description provides clear guidance on when to use the tool, including the default behavior when no activity ID is given. It references 'list_activities' as a way to find IDs. However, it does not explicitly contrast with alternative log tools like 'get_environment_logs'.

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

Deploy Server