Paidnice

List inbound email

list_inbound_email

Read-onlyIdempotent

Returns emails the organisation received through Paidnice, most recent first, up to 100 per page. Each email shows the sender, recipients, subject, the matched contact when known, and the extracted reply text. Read only.

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": {
      "organisationId": "<organisationId>"
    },
    "name": "list_inbound_email"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of records to return
`cursor`	No	Opaque cursor from a previous response's nextCursor. Omit to start from the most recent record.
`organisationId`	Yes	Id of the organisation to act on, from list_organisations

Output Schema

Name	Required	Description	Default
`data`	Yes
`nextCursor`	No	Pass as the cursor query parameter to fetch the next page. Absent on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description's closing 'Read only' is largely redundant. It does add genuine context beyond the annotations: results are ordered most recent first, capped at 100 per page, and each item includes sender, recipients, subject, matched contact, and extracted reply text.

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 short sentences with the resource, ordering, page size, and returned fields front-loaded. Every clause carries information and there is no filler or repetition of the tool name.

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?

An output schema exists, so return values need not be explained, yet the description helpfully summarizes the payload shape. With all three parameters documented in the schema and safety covered by annotations, the only gap is guidance on choosing this tool over its siblings.

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 100%, so limit, cursor, and organisationId are already documented in the schema, which sets the baseline at 3. The description's 'up to 100 per page' echoes the limit maximum but adds no new detail about the cursor or the organisationId lookup.

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 a specific verb and resource: it 'Returns emails the organisation received through Paidnice', and it names the ordering and page cap. It does not explicitly contrast itself with the sibling list_inbound_sms, leaving that differentiation to the tool name alone.

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 only implied: an agent can infer this is the way to read inbound email for an organisation, but there is no statement of when to prefer it over siblings such as list_inbound_sms, get_contact, or list_actions, and no prerequisites or exclusions are given.

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

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