Taseli

The ad accounts

list_accounts

Read-onlyIdempotent

Every ad account of this business that Taseli runs: Google Ads, Meta and TikTok, each with its id, platform, currency, goal and target, monthly budget and spend so far, totals over the last 28 complete days (the app's window), when it last synced and whether it is read only (nothing changes in it, even approved).

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"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No

Output Schema

Name	Required	Description
`note`	No	A plain note instead of data (nothing connected yet, not available here).
`total`	No	How many there are in all.
`accounts`	No
`truncated`	No
`nextCursor`	No
`truncatedNote`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds useful context: totals use the app's 28-complete-day window, accounts show last sync time, and read-only means nothing changes even if approved. It does not describe pagination or rate limits, which are minor gaps for a read-only list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence that spends its clauses on returned fields rather than filler. It is dense but efficient; a short break or pagination note could improve scanability, but there is little wasted wording.

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

Completeness3/5

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

Because an output schema exists and annotations cover the safety profile, the description does not need to explain return values, yet it helpfully summarizes them. However, it omits the semantics of the limit and cursor inputs, which matters for a paginated list tool.

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

Parameters1/5

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

The schema has two parameters, limit and cursor, with zero description coverage, and the description never mentions pagination, limits, or cursor semantics. The agent gets no guidance on how to control page size or continue paging.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (every ad account of this business) and enumerates platforms and fields, so the agent knows exactly what the tool returns. It does not explicitly contrast with sibling tools such as get_business, but the ad-account scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the content: call this to retrieve all ad accounts with budgets, spend, and sync status. There is no explicit when-to-use or when-not guidance and no named alternative, so the agent must infer the context.

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

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