axure-mcp-server

axure_fetch

Extract visible text and image URLs from public Axure share links for AI analysis. Supports multi-page crawling and OCR fallback to process image-only prototypes.

Instructions

Fetch visible text and image URLs from a public Axure share link.

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": {
      "url": "<url>"
    },
    "name": "axure_fetch"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Public Axure URL, e.g. https://xxx.axshare.com/?id=...
`timeoutMs`	No
`maxImages`	No
`maxTexts`	No
`crawlPages`	No	If true, discovers and crawls additional same-origin Axure links.
`maxPages`	No
`enableOcrFallback`	No	If true, OCR fallback will run when extracted text is too little.
`ocrMinTextCount`	No
`ocrMaxImages`	No
`ocrLanguage`	No	Tesseract language codes, e.g. chi_sim+eng
`includeImageBase64`	No	If true, tries to attach image base64 data for each URL.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Mar 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions fetching text and image URLs but fails to describe critical traits like rate limits, authentication needs, error handling, or what the output looks like (e.g., format, structure). For a tool with 11 parameters and no output schema, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resources, making it easy to grasp quickly. Every part of the sentence earns its place by specifying what is fetched and from where.

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

Completeness2/5

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

Given the complexity (11 parameters, no annotations, no output schema), the description is insufficiently complete. It doesn't address output format, error conditions, performance expectations, or how parameters interact (e.g., 'crawlPages' with 'maxPages'). For a data-fetching tool with many configuration options, more context is needed to use it effectively.

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 45%, meaning many parameters lack descriptions in the schema. The tool description adds no parameter-specific information beyond implying the 'url' parameter is for Axure links. It doesn't explain the purpose or interplay of parameters like 'timeoutMs', 'maxImages', or 'crawlPages', offering minimal compensation for the low schema coverage.

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 ('Fetch') and the resources ('visible text and image URLs') from a specific source ('public Axure share link'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'axure_health' or 'axure_summary_prompt', which might have overlapping or related functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its siblings ('axure_health' and 'axure_summary_prompt'), nor does it mention any prerequisites, exclusions, or alternative scenarios. Usage is implied only by the tool's name and description, lacking explicit context for selection.

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

Deploy Server