Skip to main content
Glama

list_recruiting_site_accounts

Read-only

List the recruiting portals the user has connected in the Auto Apply app and their sign-in state (no credentials). The state is what the app last verified. (Requires the user's sign-in with scope job_applications:read.)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world, so the safety profile is covered. The description adds value beyond that: it discloses that credentials are never returned and that the state reflects only what the app last verified — a staleness caveat an agent would otherwise not know — plus the required auth scope job_applications:read.

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?

Two short sentences plus a parenthetical auth note, all front-loaded with the core purpose first and the exclusion ('no credentials') immediately after. The parenthetical nesting is slightly clunky but nothing is redundant.

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?

For a zero-parameter, read-only listing tool with no output schema, the description covers what is returned (portals plus sign-in state), what is excluded (credentials), how fresh the data is, and the required auth scope — everything an agent needs to call it and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is empty, so there is nothing parameter-level to explain; the baseline for a no-param tool applies. The description correctly avoids inventing inputs and instead spends its words on return content.

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?

The description names a specific verb and resource — 'List the recruiting portals the user has connected in the Auto Apply app' — and further specifies the payload (sign-in state, explicitly no credentials). That is enough for an agent to distinguish it from sibling list_* tools covering resumes, exams, interviews, and knowledge bases.

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?

The narrow scope implies when the tool applies (checking which recruiting portals are linked and whether each is still signed in), and the scope requirement hints at a precondition. However, it never states when to prefer this over other list tools or what to do if the result is empty, so usage remains inferred rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources