runwayMCP

by satovarb16

Overview Schema Source Related Servers Discussions Admin

Python

Local

list_jobs

Retrieve stored job records filtered by company, status, score, or date, with configurable sorting and limits.

Instructions

Return stored job records with optional filtering, sorting, and limiting.

Pipeline order: FILTER -> SORT -> LIMIT, expressed as WHERE/ORDER BY/ LIMIT (D9). Arguments are validated in Python BEFORE any SQL is built, so an invalid status still produces the "use one of: ..." message rather than a raw SQL error. This tool NEVER raises.

Args: since: ISO-8601 string cutoff (inclusive). status: One ApplicationStatus value, or a list to match any member. min_score: Minimum score threshold (inclusive). None scores excluded. company: Substring match against company, case-insensitive (lower() on both sides, ASCII-only — SQLite's lower() does not fold non-ASCII). This is SC-1, the release's headline query ("did I apply to Acme?") — D9. limit: Maximum number of records to return (after sort). sort_by: "analyzed_at" (default, newest first) or "score" (descending, None scores last).

Returns: ListJobsResult with success=True and filtered/sorted records on success; success=False with error_message on failure.

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`since`	No
`status`	No
`company`	No
`sort_by`	No	analyzed_at
`min_score`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`jobs`	No
`count`	No
`success`	Yes
`error_message`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.0Sep 19, 2026

addedOutput schema / $defs / StoredJob / properties / status_notes

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Status Notes"
+}

Addedv0.3.1Sep 12, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses that the tool NEVER raises, validates arguments before building SQL, communicates validation failures through error_message, preserves pipeline order, and handles edge cases like None scores and ASCII-only case folding.

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?

The description is well-organized: a one-line summary, pipeline/validation context, detailed Args, and Returns. Some internal markers like 'SC-1' and 'D9' add minor noise, but every substantive sentence contributes to correct invocation.

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?

Given six optional parameters, zero annotations, and no schema-level descriptions, this description is complete enough for correct use. It explains filtering, sorting, limiting, validation, failure behavior, and default ordering; the output schema covers the return shape.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must document all parameters, and it does. Each of the six parameters gets meaningful detail: inclusive cutoffs, list-or-single status, None exclusions, case-insensitive substring matching, limit after sort, and sort_by valid values with defaults.

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 opening sentence 'Return stored job records with optional filtering, sorting, and limiting' clearly identifies an action and resource. The plural 'records' implies this is a listing tool rather than a single-record fetcher like get_job, but it does not explicitly name or differentiate from sibling tools.

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 explicit guidance on when to use this tool versus alternatives such as get_job or other job-related tools. The description focuses on mechanics and semantics rather than usage context or exclusions, leaving the agent to infer when this is the right choice.

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

Deploy Server