LeanrIQ

get permissions

get_permissions

Read-onlyIdempotent

get permissions. Classification: read-only. Execution: synchronous. Task support: forbidden. The returned JSON is internal application state for LeanrIQ and ChatGPT orchestration. Use assistantSummary first when responding to the user. Never display raw JSON, data, or meta unless the user explicitly asks for raw JSON. Mention IDs only when useful for follow-up or debugging. Prefer concise, human language, highlight the most useful insight, and suggest the next best LeanrIQ action.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`seatId`	No
`seatName`	No
`accountId`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes
`error`	No
`status`	Yes
`assistantSummary`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedAug 12, 2026

TDQS

C2.7/5.0

Behavior4/5

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

The description discloses several behavioral traits beyond annotations: execution is synchronous, task support is forbidden, and the returned JSON is internal application state not to be displayed raw. These add useful context and do not contradict the readOnlyHint/idempotentHint/destructiveHint annotations.

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

Conciseness2/5

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

The description is a long paragraph mixing tool purpose with response-format instructions (e.g., 'Never display raw JSON', 'Suggest the next best LeanrIQ action'). This is bloated and not appropriately front-loaded; much of the content belongs in a system prompt rather than a tool description.

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

Completeness2/5

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

While the tool has an output schema and some behavioral context (read-only, synchronous, internal state), the description lacks usage guidelines and parameter semantics. For a tool with three undocumented parameters and no guidance on when to use it, the description is incomplete despite the output schema covering return values.

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?

Schema description coverage is 0% and the description does not explain any of the three parameters (seatId, seatName, accountId). The description entirely fails to compensate for the missing schema descriptions, leaving the agent with no semantic guidance for parameters.

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 states 'get permissions' as a specific verb+resource, clearly indicating the tool retrieves permission information. However, it does not explicitly differentiate this tool from the many other 'get_*' tools in the sibling list, so it earns a 4 rather than a 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions 'Task support: forbidden' which is a restriction, but does not state appropriate use cases or point to sibling tools. This is minimal guidance at best.

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

All LeanrIQ tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.6/5.0

Disambiguation2/5

The tool set is dominated by deprecated aliases (leanriq_build_ad, leanriq_create_brief, etc.) that duplicate canonical tools exactly, and multiple high-level builders (build_ad, build_campaign_creative_set, leanriq_campaign_builder, launch_creative_campaign) overlap in purpose. An agent would struggle to pick the intended tool without inspecting full descriptions.

Naming Consistency2/5

Canonical tools follow a sensible verb_noun pattern (create_campaign, get_creative, list_flights), but the large number of 'leanriq_' prefixed aliases and special names like leanriq_campaign_builder create a mixed, inconsistent surface. The presence of both build_ad and leanriq_build_ad, or get_current_seat and leanriq_current_seat, breaks any predictable convention.

Tool Count1/5

87 tools is an extreme number for any MCP server, even a broad ad-platform API. The sheer volume, including many duplicate aliases, far exceeds a well-scoped set and will overwhelm agents with unnecessary choices.

Completeness4/5

The core lifecycle is well covered: CRUD for advertisers, campaigns, flights, creatives, versions, assets, plus trafficking, QA, preview, and publishing. Minor gaps exist, such as the missing canonical create_creative_strategy (only a deprecated alias references it) and no direct update_creative, but the domain is functionally complete.

Resources

Need Help?