agentaeo-mcp-server

download_aeo_content_suite_zip

Download the completed Content Suite ZIP file from the AGENTAEO MCP server to analyze brand visibility and improve AI-generated answer rankings.

Instructions

Download the Content Suite ZIP after status is completed (same AGENTAEO_API_KEY as generate). Saves to cwd or AGENTAEO_MCP_DOWNLOAD_DIR.

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": {
      "orderId": "<orderId>"
    },
    "name": "download_aeo_content_suite_zip"
  }
}

Input Schema

Name	Required	Description	Default
`orderId`	Yes	orderid UUID from generate_aeo_content_suite / check_aeo_content_suite_status
`outputFileName`	No	Optional filename, e.g. content-stripe.zip (default: content-suite-<first8ofuuid>.zip)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.7Mar 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool saves files to specific directories (cwd or AGENTAEO_MCP_DOWNLOAD_DIR) and requires the same API key as 'generate', which adds useful context. However, it doesn't mention potential errors, file size limits, or authentication requirements beyond the API key reference.

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 appropriately concise with two sentences that each serve a clear purpose: first stating the action and prerequisites, second describing the output behavior. It could be slightly more structured but wastes no words.

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?

For a download tool with no annotations and no output schema, the description provides adequate but minimal context. It covers the prerequisite state and output location, but doesn't explain what happens on failure, file format details, or return values. Given the tool's relative simplicity, this is minimally sufficient.

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 description coverage is 100%, so the schema already fully documents both parameters. The description doesn't add any meaningful parameter semantics beyond what's in the schema descriptions, so it meets the baseline of 3.

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 action ('Download') and resource ('Content Suite ZIP'), and distinguishes it from siblings by referencing the 'generate' tool. However, it doesn't explicitly differentiate from 'check_aeo_content_suite_status' which is about status checking rather than downloading.

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 context for when to use this tool ('after status is **completed**') and references the prerequisite 'generate' tool. It doesn't explicitly state when NOT to use it or name alternatives, but the context is sufficiently clear.

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

Deploy Server