Skip to main content
Glama
Sign In

Selenios

by com.selenios.back
OverviewDiscussionsAdmin

List job positions

list_jobs
Read-onlyIdempotent

List job positions/descriptions for the organization. Returns job title, department, location, status, and candidate counts. Paginate with cursor (from pageInfo.nextCursor) and sync incrementally with updatedSince.

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_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRecords per page (default: 20, max: 1000). Values above ~50 are meant for programmatic syncing, not for reasoning over the results.
cursorNoOpaque cursor from the previous page (`pageInfo.nextCursor`). Omit for the first page. Treat it as a token — do not construct or modify it.
sortByNoSort field (default: createdAt).
statusNoFilter by status
sortOrderNoSort order (default: desc).
updatedSinceNoISO 8601 timestamp. Returns only records modified strictly after it, for incremental syncing. Deleted records are never returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for adding return-field composition, cursor chaining from pageInfo.nextCursor, and incremental-sync semantics. It omits any note on ordering guarantees or what happens for large result sets, which keeps it from 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?

Three short sentences: identity of the resource, payload contents, then pagination/sync mechanics. Front-loaded and every sentence carries information.

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?

For a read-only list tool with no output schema, the description covers return shape and pagination adequately. It is slightly thin on the filtering and sorting capabilities the schema exposes, which an agent calling it would want surfaced.

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 all six parameters including enums are self-documenting; baseline is 3. The description only reiterates cursor and updatedSince, both already described in the schema, and never mentions the status/sortBy/sortOrder filters or the limit ceiling.

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 ('List job positions/descriptions for the organization') and enumerates the returned fields, so the agent knows exactly what it gets. It does not distinguish itself from siblings like get_job_description or search_candidates, so it stops short of 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 Guidelines3/5

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

Gives how-to-use mechanics (paginate with cursor, sync incrementally with updatedSince) but no explicit when-to-use-this-vs-alternative guidance, e.g. it never says to use get_job_description for a single posting or search_candidates when filtering by candidate attributes. Usage is implied by context rather than stated.

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

All Selenios toolsInspect
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