Shortimize

List Collection Accounts

get_collection_accounts

Read-onlyIdempotent

List the accounts that belong to one collection, identified by collection_id, with sorting and pagination (page, limit, order_by, order_direction). Use it to review one collection's accounts; use get_all_accounts to search across all accounts, and add_accounts_to_collection or remove_accounts_from_collection to change membership. Returns { data, pagination }. Tier limits: Limited/Basic keys get 1 result with masked metrics; Premium gets full access.

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": {
      "collection_id": "<collection_id>"
    },
    "name": "get_collection_accounts"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number (default: 1)
`limit`	No	Items per page (default: 100, max: 5000)
`order_by`	No	Field to order by	created_at
`paginated`	No	Set to true to receive paginated response with {data, pagination} format instead of raw array
`collection_id`	Yes
`order_direction`	No	Order direction	desc

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds genuinely new context: tier-based behavior (Limited/Basic keys get 1 result with masked metrics; Premium gets full access) and the return shape. It loses a point because it asserts 'Returns { data, pagination }' unconditionally while the schema's paginated flag defaults to false, which would yield a raw array.

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?

Three dense sentences, each earning its place: the first defines scope and parameters, the second routes to alternatives, the third covers return shape and tier limits. The routing constraint is front-loaded right after the purpose rather than buried.

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 no output schema, the description correctly supplies the return shape and adds tier-limit behavior that the schema cannot express. The only gap is that it does not clarify that the { data, pagination } envelope requires paginated=true, leaving a subtle mismatch with the schema default.

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 83%, so the schema already documents page, limit, order_by, and order_direction with defaults and the limit maximum. The description merely names the same four parameters without adding format, constraints, or edge-case behavior, so it does not exceed the baseline for well-covered schemas.

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 accounts that belong to one collection, identified by collection_id') and immediately scopes it against the sibling get_all_accounts, which searches across all accounts. An agent can distinguish this from get_collection, get_collection_videos, and get_all_accounts 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 Guidelines5/5

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

Explicitly names the when (review one collection's accounts) and three alternatives with their selecting conditions: get_all_accounts for cross-collection search, and add_accounts_to_collection / remove_accounts_from_collection for changing membership. This is textbook routing guidance.

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

All Shortimize 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.