AdaptlyPost

Refresh Inbox

refresh_inbox

Idempotent

Queue an inbox sync for every connected account now instead of waiting for the next 10-minute run. It returns at once with { queued: true }; new items show up in the list tools a minute or so later, so do not poll in a tight loop. Nothing is sent to anyone. Needs the inbox.read permission, which every role holds. Takes only the optional workspaceId.

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

Input Schema

Name	Required	Description	Default
`workspaceId`	No	Workspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

Name	Required	Description	Default
`result`	Yes	An object with queued: true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 9, 2026
- addedOutput schema / properties / result / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / result / properties
```
Added value: +{
+  "queued": {
+    "type": [
+      "boolean",
+      "null"
+    ]
+  }
+}
```
- addedOutput schema / properties / result / type
```
Added value: +"object"
```
- addedOutput schema / required
```
Added value: +[
+  "result"
+]
```
AddedNov 8, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: immediate return with { queued: true }, eventual-consistency delay before items appear, and that nothing is sent to anyone. It stops short of naming failure modes or what happens if a sync is already running.

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?

Five short sentences, front-loaded with the action and immediately followed by the return behavior and the polling warning. Every sentence carries distinct information (timing, permission, scope); nothing is filler.

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?

A mutation-ish async trigger with rich annotations and an output schema — the remaining burdens are latency semantics and auth requirements, and the description covers both (items appear a minute later, inbox.read held by every role). Nothing an agent needs to invoke it correctly is missing.

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 workspaceId property already documents sourcing the id from list_workspaces, omitting it for the current workspace, and cross-workspace id non-portability. The description only restates that workspaceId is the sole, optional parameter, adding no meaning beyond the schema — baseline 3.

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?

States a specific verb and resource ('Queue an inbox sync') plus the scope ('every connected account now'), and contrasts it with the passive alternative of 'waiting for the next 10-minute run'. An agent can tell it apart from the list_inbox_* readers without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger (want fresh items before the scheduled run), an explicit anti-pattern ('do not poll in a tight loop'), and routes the agent to 'the list tools' after a minute or so for reading results. Both when-to-call and when-not-to-call are stated.

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

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