Parse
Pricing
Sign inCheck your brand

Docs

Fetch

  • Start here
  • Get started
  • Workflows
  • MCP reference
  • Plans and limits
  • Data and trust
  • Changelog

fetch: compatibility names tool on Parse's MCP server.

Compatibility alias that resolves fetch IDs like brand:stripe, topic:<id> or question:best-crm into JSON-text results with human-readable text.

Who may call it

NameAccessPlanEffect
fetchNo sign-in. Generic search and fetch for clients that expect them.Any, no accountReads only

Input

ArgumentTypeRequiredNotes
idstringyes
json
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    }
  },
  "required": [
    "id"
  ]
}

Example call

POST to https://mcp.parse.gl/mcp with Content-Type: application/json and Accept: application/json, text/event-stream:

json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "fetch",
    "arguments": {
      "id": "<id>"
    }
  }
}

Limits

Every request: 100 per 10 seconds and 120 a minute per network address. Without sign-in, reads of one brand, topic or question in full: 20 a minute. All limits are on Plans and limits.

This page as Markdown

See where your brand stands in AI answers

Free. About a minute. No sign-up.

Parse

Know where you stand. Find your next opportunity.

Products

  • Brands
  • Markets
  • Topics
  • Work with us
  • Pricing

Resources

  • Research
  • Methodology
  • Blog
  • MCP
  • Docs
  • For AI
  • llms.txt

Compare

  • Parse vs Profound
  • Parse vs Peec AI
  • Parse vs AthenaHQ
  • Parse vs Scrunch
  • Parse vs Otterly.AI
  • All comparisons

Company

  • About
  • Dimitry Apollonsky
  • Contact us
  • Corrections

© 2026 Parse, Inc. All rights reserved.

Privacy PolicyTerms of Service