Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Check Account

check_account
Idempotent

Re-checks a Facebook page with its stored token to return fresh status, clear unauthorized marks after reconnects, or flag rejected tokens when posts fail.

Instructions

Re-check a Facebook page with Facebook now, using its stored token, and return its fresh status. A rejected token marks the page unauthorized (unauthorizedReason carries Facebook's message); a working token clears an earlier unauthorized mark. Facebook pages only: any other account fails with 400. Pages are also checked automatically twice a day. Use it after the user reconnects or fixes a page, or when a Facebook post failed with a token error. Needs the accounts.manage permission, which Admin holds. Nothing is posted.

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": {
      "accountId": "<accountId>"
    },
    "name": "check_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesThe Facebook account id from list_accounts, or its pageId
workspaceIdNoWorkspace 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

NameRequiredDescriptionDefault
resultYesAn object with id, platform, displayName, pageId, status (active or unauthorized), unauthorizedReason when unauthorized, and checkedAt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description still adds real context beyond that: it performs a live call to Facebook, a rejected token writes an unauthorized mark with Facebook's message in unauthorizedReason, a working token clears that mark, and nothing is posted. It omits rate-limit or latency behavior for an external API call, which keeps it short of a 5.

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?

Front-loaded with the action and its outcome, then scope, then side effects, then preconditions. Each sentence carries distinct information — state transitions, error behavior, automatic scheduling, permissions, and the no-post guarantee — with no repetition.

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?

With an output schema present, return values need no explanation, yet the description still flags the key field (unauthorizedReason) an agent must interpret. It also covers the permission requirement (accounts.manage, held by Admin), the external-call nature, and the state-mutation semantics for a two-parameter tool.

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%, so accountId (from list_accounts or its pageId) and workspaceId are already fully documented in the schema. The description adds the semantic point that the token is stored server-side rather than passed in, but contributes nothing further about parameter formats or constraints. Baseline 3 is appropriate.

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 — 'Re-check a Facebook page with Facebook now, using its stored token, and return its fresh status' — including the live-verification mechanism (stored token) that distinguishes it from a passive read. The scope line 'Facebook pages only: any other account fails with 400' separates it from the RSS/other-account siblings.

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 explicit triggering conditions ('after the user reconnects or fixes a page, or when a Facebook post failed with a token error') plus an implicit when-not ('Pages are also checked automatically twice a day'), telling the agent the manual check is not routine. It also names the failure mode (400) for non-Facebook accounts, so wrong selections are caught early.

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

Deploy Server

Other Tools