Markaestro

Official

by markaestro

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

List destinations

list_destinations

Read-onlyIdempotent

Retrieve a brand's publishable destinations with IDs and delivery modes to choose the right destinationId for create_post when a channel has multiple destinations.

Instructions

List the publishable destinations (Facebook Page, Instagram account, TikTok account, ...) of a brand, with their ids and delivery modes. Use a destinationId on create_post only when a channel has more than one destination.

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": {
      "productId": "<productId>"
    },
    "name": "list_destinations"
  }
}

Input Schema

Name	Required	Description	Default
`productId`	Yes	Brand id from list_products

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Sep 27, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds useful specifics about what is returned (ids and delivery modes) and the destination types, but says nothing about pagination, auth requirements, or ordering.

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, front-loaded with the core action and scope, followed by the actionable integration hint. No filler.

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?

For a read-only list tool with full annotation coverage and no output schema, the description is nearly complete: it explains what is listed and why the result matters for create_post. Only minor gaps (pagination/ordering) remain.

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?

With a single parameter at 100% schema coverage, the schema already documents productId and its source. The description only implies the brand/product scope via 'of a brand' and adds no format or edge-case detail beyond the schema.

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?

States a specific verb and resource ('List the publishable destinations ... of a brand'), enumerates examples (Facebook Page, Instagram account, TikTok account), and names the returned fields (ids and delivery modes). It is clearly distinguishable from siblings like list_products or list_posts.

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 second sentence gives a concrete consumption rule: use a destinationId on create_post only when a channel has more than one destination. This ties the tool to create_post and tells the agent when the output matters, though it doesn't formally state when not to call this list tool itself.

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