Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Check the Instagram session

check_account_session

Queues a session check for an Instagram account and lets the worker update account status, helping verify whether the session is still valid.

Instructions

Check the Instagram session. Required API key scope: accounts:write. POST /accounts/{id}/check-session Queues a session check; the account status is updated by the worker.

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": {
      "id": "<id>"
    },
    "name": "check_account_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and the description adds genuinely useful context beyond them: the required scope (accounts:write) and the fact that the operation is asynchronous — it queues a check and the worker updates status later. It stops short of saying how long the check takes or how the agent should observe the result.

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?

Four short lines, front-loaded with the purpose, then scope, endpoint, and async behavior — no filler. The opening line largely restates the title, which is the only near-redundancy.

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?

For a non-read-only, non-idempotent action with no output schema, the description covers the essentials (scope, endpoint, async nature). However, it never says which sibling tool to poll afterward to learn the resulting account status, leaving a real gap for an agent that needs the outcome.

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 the baseline is 3. The description does add a little meaning by showing the path pattern /accounts/{id}/check-session, which confirms the single `id` parameter is an account id rather than a session id, but it provides no further detail on that parameter.

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?

States a specific verb and resource ('Check the Instagram session') and backs it with the concrete endpoint POST /accounts/{id}/check-session, so the agent knows exactly what operation runs. It does not explicitly distinguish itself from nearby siblings like relogin_account or get_login_status, which keeps it from 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?

There is no when-to-use or when-not-to-use guidance and no naming of alternatives among the many account-related siblings (relogin_account, get_login_status, verify_account_2fa, verify_account_challenge). The agent must infer from the name alone which account-health tool applies to its situation.

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