JobMojito

List tasks

list_tasks

Read-onlyIdempotent

[Tasks] The hiring team's follow-up tasks: mine, created by me or all; by candidate, position, assignee, status or due date; with counts.

Every argument in full, with examples: get_tool_reference.

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

Input Schema

Name	Required	Description	Default
`due`	No	Only open tasks overdue, due today (company time zone), upcoming, or without a due date (none).
`limit`	No	Tasks per page (1 to 500, default 50).
`scope`	No	mine (assigned to you, default), created (created by you) or all (every task of the company; owners only).	mine
`offset`	No	Number of records to skip from the start of the result set.
`status`	No	open (default), done, cancelled or all.	open
`llm_model`	No	Your model id, e.g. "claude-opus-4-8"; "unknown" if unsure. For analytics.
`merchant_id`	No	Optional merchant to scope to. Admins and sub-merchant operators only; other callers always use their token's merchant.
`position_id`	No	Only tasks about this position (a position `id` from list_interviews) or interview (an interview `id` from list_interviews) itself.
`candidate_id`	No	Only tasks about this candidate (the `id` of a list_candidates row), including those about one of their applications.
`conversation_id`	No	The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
`assignee_profile_id`	No	Only tasks assigned to this user (`profile_id` (list_users)). Without candidate_id and position_id this lists a team member's tasks: owners only.

Output Schema

Name	Required	Description
`data`	Yes
`counts`	Yes
`truncated`	Yes
`pagination`	Yes
`_mcp_instructions`	No	Server-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 9, 2026

changedInput schema / properties / assignee_profile_id / description

Previous value: -"Only tasks assigned to this user (profile.id). Without candidate_id and position_id this lists a team member's tasks: owners only."New value: +"Only tasks assigned to this user (`profile_id` (list_users)). Without candidate_id and position_id this lists a team member's tasks: owners only."

changedInput schema / properties / candidate_id / description

Previous value: -"Only tasks about this candidate (profile_interview.id), including those about one of their applications."New value: +"Only tasks about this candidate (the `id` of a list_candidates row), including those about one of their applications."

changedInput schema / properties / position_id / description

Previous value: -"Only tasks about this position (position_def_set.id) or interview (interview_def_set.id) itself."New value: +"Only tasks about this position (a position `id` from list_interviews) or interview (an interview `id` from list_interviews) itself."

Changed40 schema fields changedNov 9, 2026
- removedInput schema / properties / limit / example
```
Removed value: -50
```
- addedInput schema / properties / llm_model
```
Added value: +{
+  "description": "Your model id, e.g. \"claude-opus-4-8\"; \"unknown\" if unsure. For analytics.",
+  "type": "string"
+}
```
- removedInput schema / properties / merchant_id / example
```
Removed value: -"28106cba-1c27-4e53-b149-32113e5e8e31"
```
- removedInput schema / properties / offset / example
```
Removed value: -0
```
- changedInput schema / properties / scope / description
```
Previous value: -"mine (assigned to you, default), created (created by you) or all (every task of the company; owners only). Ignored with candidate_id, position_id or assignee_profile_id."New value: +"mine (assigned to you, default), created (created by you) or all (every task of the company; owners only)."
```
- removedOutput schema / properties / counts / description
```
Removed value: -"Your own open tasks (as the To do menu shows them), whatever the filters."
```
- removedOutput schema / properties / counts / properties / open / description
```
Removed value: -"Your open tasks (assigned to you)."
```
- removedOutput schema / properties / counts / properties / overdue / description
```
Removed value: -"Of those, overdue."
```
- removedOutput schema / properties / counts / properties / today / description
```
Removed value: -"Of those, due today (company time zone)."
```
- removedOutput schema / properties / data / description
```
Removed value: -"Tasks of this page: open ones overdue first, then due today, upcoming, without a due date; then done and cancelled, newest first."
```
- removedOutput schema / properties / data / items / properties / admin_path / description
```
Removed value: -"Path of the task subject in the JobMojito admin (append to the admin host)."
```
- removedOutput schema / properties / data / items / properties / application_id / description
```
Removed value: -"Application the task is about (position_result.id)."
```
- removedOutput schema / properties / data / items / properties / assignee_name / description
```
Removed value: -"Assignee's name, or e-mail when the name is empty."
```
- removedOutput schema / properties / data / items / properties / assignee_profile_id / description
```
Removed value: -"Assignee (profile.id of a company user)."
```
- removedOutput schema / properties / data / items / properties / can_complete / description
```
Removed value: -"You may change the status."
```
- removedOutput schema / properties / data / items / properties / can_edit / description
```
Removed value: -"You may change title, notes, assignee and due date (creator, assignee or owner)."
```
- removedOutput schema / properties / data / items / properties / candidate_id / description
```
Removed value: -"Candidate the task is about (profile_interview.id)."
```
- removedOutput schema / properties / data / items / properties / candidate_name / description
```
Removed value: -"Candidate's name."
```
- removedOutput schema / properties / data / items / properties / completed_at / description
```
Removed value: -"When the task was marked done (ISO 8601)."
```
- removedOutput schema / properties / data / items / properties / created_at / description
```
Removed value: -"When the task was created (ISO 8601)."
```
- removedOutput schema / properties / data / items / properties / created_by / description
```
Removed value: -"Who created the task (profile.id)."
```
- removedOutput schema / properties / data / items / properties / created_by_name / description
```
Removed value: -"Creator's name, or e-mail when the name is empty."
```
- removedOutput schema / properties / data / items / properties / definition_id / description
```
Removed value: -"Position (position_def_set.id) or interview (interview_def_set.id) the task is about; see definition_kind."
```
- removedOutput schema / properties / data / items / properties / definition_kind / description
```
Removed value: -"What definition_id is: position or interview."
```
- removedOutput schema / properties / data / items / properties / definition_name / description
```
Removed value: -"Name of the position or interview."
```
- removedOutput schema / properties / data / items / properties / due_at / description
```
Removed value: -"Due date and time (ISO 8601). Left out when the task has no due date."
```
- removedOutput schema / properties / data / items / properties / due_state / description
```
Removed value: -"overdue (the due time has passed), today (due today in the company time zone), upcoming, or none (no due date, or not open)."
```
- removedOutput schema / properties / data / items / properties / id / description
```
Removed value: -"Task id (merchant_task.id)."
```
- removedOutput schema / properties / data / items / properties / notes / description
```
Removed value: -"Notes, at most 4000 characters. Left out when empty."
```
- removedOutput schema / properties / data / items / properties / status / description
```
Removed value: -"open, done or cancelled (cancelled is final)."
```
- removedOutput schema / properties / data / items / properties / title / description
```
Removed value: -"Title, 1 to 200 characters."
```
- removedOutput schema / properties / pagination / properties / has_more / description
```
Removed value: -"True when more records exist beyond this page (offset + returned < total)."
```
- removedOutput schema / properties / pagination / properties / has_more / example
```
Removed value: -true
```
- removedOutput schema / properties / pagination / properties / limit / description
```
Removed value: -"Page size used for this response."
```
- removedOutput schema / properties / pagination / properties / limit / example
```
Removed value: -50
```
- removedOutput schema / properties / pagination / properties / offset / description
```
Removed value: -"Offset used for this response."
```
- removedOutput schema / properties / pagination / properties / offset / example
```
Removed value: -0
```
- removedOutput schema / properties / pagination / properties / total / description
```
Removed value: -"Total matching records across all pages."
```
- removedOutput schema / properties / pagination / properties / total / example
```
Removed value: -137
```
- removedOutput schema / properties / truncated / description
```
Removed value: -"true when more than 500 tasks matched the database query: only the first 500 can be paged and counted. Narrow the filters."
```
AddedNov 8, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds only 'with counts' as a return-behavior hint and otherwise repeats scoping that already appears in the schema; nothing is said about pagination limits, permission boundaries, or result ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the resource front-loaded, which is good. However, the second sentence defers all argument detail to get_tool_reference, which is wasted space given the schema already documents every parameter fully.

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?

With a full output schema, 11 thoroughly described parameters, and annotations covering the safety profile, the description supplies enough for an agent to call the tool correctly. Only the counts semantics and the relationship to sibling listing tools remain unstated.

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 description coverage is 100%, so every parameter including the enums and the owner-restriction on 'all' is already documented in structured fields. The description's filter list mirrors the schema rather than adding syntax, defaults, or interaction rules, so baseline 3 applies.

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?

The description names the resource (the hiring team's follow-up tasks), the scope modes (mine, created by me, all), and the filter dimensions (candidate, position, assignee, status, due date), which clearly separates it from mutation siblings like save_task. It stops short of a verb-first phrasing, but the intent is unambiguous.

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?

Usage is only implied through the enumerated filter modes; there is no explicit statement of when to call this versus alternatives (e.g., get_candidate or list_interviews for related data). No exclusions or prerequisites are given, so the agent must infer selection from the name and schema.

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

All JobMojito 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.