Skip to main content
Glama
tokportal

tokportal-mcp

Official
by tokportal

tokportal_list_account_bans

Read-onlyIdempotent

Retrieve a paginated, pollable list of validated ban reports and appeals for delivered accounts. Filter by lifecycle status, staff resolution, account ID, and use the since watermark to track status changes and new reports.

Instructions

List ban reports and appeals. Pollable list of validated ban reports for the caller's delivered accounts, covering the whole lifecycle: appeal_pending (platform appeal filed, account unavailable but NOT yet banned), appeal_accepted (account survived), appeal_refused / no_appeal_banned (confirmed ban), and the staff commercial resolution (refund / remake / no_remake with a machine-readable reason_code such as tos_ban). This is the REST counterpart of the account.banned, account.ban_appeal.submitted, account.ban_appeal.resolved and account.ban_resolution.decided webhook events. Only staff/CM-validated bans appear here — detections from TokPortal's internal health scan are never listed. Poll with the since parameter (updated_at watermark) to pick up new reports and status changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number.
sinceNoOnly reports updated at or after this ISO 8601 timestamp. Use the highest updated_at you have seen as a polling watermark.
statusNoFilter by appeal lifecycle status.
per_pageNoItems per page.
account_idNoFilter by saved account ID.
resolutionNoFilter by staff commercial resolution. 'pending' selects confirmed bans still awaiting the staff decision.
include_screenshotsNoWhen true, each report includes a signed 7-day URL of the ban-evidence screenshot when one exists.
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds rich behavioral details: pollable list, lifecycle status meanings, resolution codes, screenshot URL behavior, and the exclusion of internal health scans. No contradictions.

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?

The description is a single well-organized paragraph. It front-loads the core purpose, then efficiently covers scope, lifecycle, polling behavior, and exclusions. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (7 parameters, multiple enums, polling, lifecycle states), the description covers all essential aspects: what is listed, what is excluded, how to poll, meaning of statuses and resolutions, and screenshot feature. No output schema is present, but the description sufficiently describes what the tool returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter already has a description. The description adds context beyond the schema, such as explaining that 'since' is a polling watermark, what each status enum value means (e.g., 'appeal_pending' means account unavailable but not yet banned), and that 'include_screenshots' provides signed 7-day URLs. This adds significant domain understanding.

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 clearly states the tool lists ban reports and appeals, covering the full lifecycle with specific statuses. It distinguishes from internal health scans and webhook events, making its unique purpose unmistakable.

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?

Provides explicit polling guidance with the 'since' parameter and explains what data is included. Tells users that only staff/CM-validated bans appear, ruling out internal health scan detections. Does not name specific sibling alternatives, but no other sibling serves the same purpose.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tokportal/langchain-tokportal'

If you have feedback or need assistance with the MCP directory API, please join our Discord server