Skip to main content
Glama

List Accounts Tool

list-accounts-tool
Read-only

List the authenticated user's posting accounts on TikTok, Instagram and YouTube, newest first, 50 per page. Every platform is included unless platform narrows it to one.

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": "list-accounts-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number to fetch (defaults to 1). Each page holds up to 50 accounts.
platformNoOnly accounts on this platform: "tiktok", "instagram" or "youtube". Omit for every platform, merged newest-first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds behavior beyond that: result ordering (newest first), fixed page size (50), per-platform merging, and that results are scoped to the authenticated user — all useful for interpreting output. It omits what happens on an out-of-range page or when an account has no postings, but the additions are substantive.

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 sentences, both load-bearing: the first establishes resource, platforms, ordering, and pagination; the second establishes the filter default. No filler and the key scoping constraints are front-loaded.

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 zero-required-parameter read tool with no output schema, the description covers everything needed to call it correctly: scope, ordering, page size, and the platform filter's default. A mention of behavior when page exceeds available results, or what fields each account record contains, would close the remaining gap.

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 coverage is 100%, and the schema already documents the page default, the 50-per-page capacity, and the omit-for-all-platforms semantics of `platform`. The description restates the platform-default rule and mentions page capacity, adding confirmation rather than new meaning, so the 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 names a specific verb and resource ("List the authenticated user's posting accounts") and pins down scope with the platforms covered, the sort order ("newest first"), and page size. An agent can distinguish it from get-account-tool or create-account-tool 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 Guidelines4/5

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

It gives a clear selection rule for the platform parameter — "Every platform is included unless `platform` narrows it to one" — which tells the agent the default behavior and when to filter. It does not explicitly route the agent to siblings such as get-account-tool for a single account, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources