Narrareach

Get import status

get_import_status

Read-onlyIdempotent

Read where the writer’s imports stand: the onboarding writing import, Substack imports (pages, notes, and articles imported, and whether voice preparation ran), blog automation sources (status, last sync, item counts), and social history imports. Statuses, counts, and error categories only; no imported text. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_import_status"
  }
}

Input Schema

Name	Required	Description	Default
`workspace`	No	Optional authorized team workspace name or id. Absence selects the authenticated user’s personal account. In a team workspace only the owner can read import status.

Output Schema

Name	Required	Description	Default
`contentSources`	Yes
`writingImports`	Yes
`substackImports`	Yes
`connectedAccount`	No
`socialHistoryImports`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 18, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new context: that it returns statuses, counts, and error categories only, and explicitly no imported text content, which sets expectations about output and privacy. It does not restate the permission rule (owner-only in team workspaces), so it falls short of a 5.

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?

Content is front-loaded with the primary resource scope and the coverage is efficient in two sentences. Minor waste: the trailing 'Read-only' duplicates the readOnlyHint annotation rather than adding information.

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?

An output schema exists, so return-value detail is unnecessary, and the description covers the breadth of import categories well. For a read-only status tool the only notable omission is a pointer to the related verification-status sibling.

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?

There is a single parameter with 100% schema description coverage; the schema fully documents the optional workspace selector and the owner-only read rule. The description adds no syntax or format detail about that parameter, so baseline 3 applies.

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 states a specific verb ('Read') and enumerates the exact resource scope: onboarding writing import, Substack imports, blog automation sources, and social history imports. No sibling covers the same ground (get_substack_verification_status is about verification, get_platform_analytics about metrics), so an agent can distinguish it without opening any schema.

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

Usage Guidelines3/5

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

The scope enumeration implies when this tool is relevant, but there is no explicit when-to-use/when-not statement and no named alternative for related queries like Substack verification status. Usage is inferable but not guided.

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

All Narrareach tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?