Mark

Resolve External Post

resolve_external_post

Keeps a post published outside Mark as an unmatched external post, or links it to an existing Mark post. Admin only. Related: list_connections, get_post.

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": {
      "externalPostId": "<externalPostId>",
      "action": "<action>"
    },
    "name": "resolve_external_post"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	keep leaves it external; link attaches it to targetPostId.
`targetPostId`	No	Existing Mark post id. Required when action is link.
`externalPostId`	Yes	Id of the unmatched external post from list_connections.

Output Schema

Name	Required	Description	Default
`appUrl`	Yes
`outcome`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already disclose the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), and the description adds the admin-only authorization requirement, which is genuinely useful. However, it does not explain the consequence of the 'link' action — e.g. whether the external post is consumed or merged — which is the key behavioral question for a resolving/mutating tool.

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?

Two tight sentences plus a short related-tools pointer; the primary purpose is front-loaded and every clause carries information (two outcomes, auth gate, id source).

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?

With an output schema, full annotation coverage, and 100% parameter documentation, the description only needs to supply purpose, auth, and routing. It does that well, though it leaves the post-link side effects unstated.

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%, with the enum values and the targetPostId/externalPostId origins documented inline, so the schema carries the parameter burden. The description adds no syntax or format detail beyond it, making the baseline 3 appropriate.

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 (resolve) with the two distinct outcomes (keep as unmatched external post vs. link to an existing Mark post) and names the resource precisely. An agent can distinguish this from generic post tools like get_post or list_connections without opening the schema.

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?

It gives a real prerequisite ('Admin only') and points to the sibling that supplies the input ('list_connections') plus get_post as related context. It stops short of an explicit when-not-to-use rule, but the context for invoking it is clear.

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

All Mark 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?