courtlistener-mcp-server

Name: courtlistener-mcp-server
Author: cyanheads

Server Details

Search US court opinions, federal dockets, judges, citations, and oral arguments via CourtListener.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 48 days
Last Tested: 2026-10-04 01:15
Transport: Streamable HTTP · MCP 2025-11-25
URL
Repository: cyanheads/courtlistener-mcp-server
GitHub Stars: 3
Server Listing: @cyanheads/courtlistener-mcp-server

TDQS

A4.3/5.0

Scored 2026-09-30 11:55 across 14 tools

Disambiguation4/5

Each tool targets a distinct resource+action, and the search/get/lookup split is generally clear. The only real overlap is courtlistener_get_citations (citation network) vs courtlistener_lookup_citation (resolving a citation string), which are distinguishable but could be momentarily confused by name; descriptions resolve it.

Naming Consistency5/5

Every tool follows the same courtlistener_verb_noun pattern (get_, search_, lookup_) with snake_case throughout. No convention mixing, highly predictable.

Tool Count5/5

14 tools is well-scoped for a legal research domain spanning opinions, dockets, judges, financial disclosures, oral arguments, courts, and citations. Each tool earns its place with no redundant entries.

Completeness4/5

Strong read-only coverage: search+get pairs for opinions, dockets, judges, disclosures, and oral arguments, plus citation network/lookup and court discovery. Minor gaps remain — no tool to fetch individual RECAP documents (referenced but not retrievable) and no dedicated party lookup beyond docket search.

Available Tools

14 tools

courtlistener_get_citationsGet Citation NetworkA

Read-only

Inspect

Retrieve the citation network for an opinion cluster. Supports two directions: "cited_by" (opinions that cite this one — measures precedential influence) and "citing" (opinions this one cites — reveals the authority chain relied on). This is the primary tool for tracing legal precedent chains. Note: the free tier supports shallow traversal — following 1–2 hops of a single case is practical; deep multi-hop analysis burns through the daily budget quickly.

ParametersJSON Schema

Name	Required	Description	Default
`court`	No	Filter results to a specific court (e.g., "scotus", "ca9"). Applies to both directions.
`cursor`	No	Pagination cursor from a previous response's next_cursor field.
`direction`	No	"cited_by" (default): opinions that cite this one — measures precedential influence and downstream adoption. "citing": opinions this one cites — reveals the authority chain the court relied on.	cited_by
`page_size`	No	Number of results to request (default 20). For direction="cited_by", CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results. direction="citing" returns at most page_size (the cited-opinion list is sliced before querying) — fewer when the opinion cites fewer than page_size distinct opinions. Either direction costs three requests against the rate limit (a case with many opinion variants costs one more per extra variant page) — keep low for multi-hop traversal.
`cluster_id`	Yes	Opinion cluster ID to retrieve citations for. Obtain from courtlistener_search_opinions or courtlistener_lookup_citation.
`filed_after`	No	Limit to citations filed after this date (ISO 8601). For "cited_by", useful for "how has this precedent been applied recently?"

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Context when no citations are returned — either that this page had no match under the filters and more pages remain, or a recovery hint echoing direction and filters.
`results`	No	Related opinions in the citation network.
`direction`	No	Direction of the citation relationship returned.
`totalCount`	No	Total citations in the requested direction. For "cited_by" it counts matching clusters with the court and filed_after filters applied. For "citing" it counts the distinct opinions this case cites, before any filter — so it exceeds what the filters make reachable, and runs higher than the result rows, which are clusters (several cited opinions in one case collapse to one row).
`next_cursor`	No	Pagination cursor for the next page; null when no more results.
`source_case_name`	No	Case name for the source cluster.
`source_cluster_id`	No	The cluster ID this citation network is for.

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds genuinely new context beyond the annotations — free-tier budget constraints, that deep multi-hop traversal 'burns through the daily budget quickly,' and that each call costs multiple rate-limit requests. It stops short of describing response shape or pagination behavior, which the output schema may cover.

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?

Three sentences with the core purpose front-loaded, followed by direction meanings and then the operational caveat. Every sentence earns its place, though the direction definitions partially duplicate schema text.

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 an output schema present, return values need not be explained, and the description covers selection (directions), cost (rate-limit/three-request note), and traversal limits — the concerns an agent needs. It omits any mention of the 'court' or 'filed_after' filters despite them being relevant to multi-hop work, leaving a small gap.

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 the schema already documents every parameter (including direction, page_size minimums, and cursor). The description restates the two directions with interpretive framing ('measures precedential influence') but adds no syntax or format detail beyond the schema; baseline 3 is appropriate.

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?

States a specific verb ('Retrieve') and resource ('citation network for an opinion cluster') and then anchors it as 'the primary tool for tracing legal precedent chains,' which distinguishes it from siblings like courtlistener_lookup_citation and courtlistener_search_opinions. An agent can select this tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Clearly explains the two usage modes ('cited_by' for precedential influence, 'citing' for the authority chain) and gives practical operational guidance ('following 1–2 hops of a single case is practical'). It lacks an explicit statement of when NOT to use it versus siblings such as lookup_citation, so it falls short of a 5.

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

courtlistener_get_docketGet DocketA

Read-onlyIdempotent

Inspect

Fetch full docket metadata and entry list for a single federal case by docket ID. Returns all available docket entries with document availability status. Documents with is_available=true have a RECAP-stored copy; others require a PACER account. Obtain docket IDs from courtlistener_search_dockets or from opinion results.

ParametersJSON Schema

Name	Required	Description
`docket_id`	Yes	Docket ID from a search result's docket_id field or from an opinion cluster result.
`entries_page`	No	Page of docket entries to fetch (1-indexed). Docket entries are page-paginated at 20 per page; pass the next_cursor from a previous response here to page through large cases.
`entries_page_size`	No	Requested docket entries per page. NOTE: CourtListener ignores this value — /docket-entries/ always returns a fixed 20-entry page regardless of what is passed. Use entries_page to reach entries beyond the first 20 (large cases can have hundreds).

Output Schema

ParametersJSON Schema

Name	Required	Description
`cause`	No	Legal cause of action.
`court`	No	Court display name for major federal courts; the court identifier otherwise.
`error`	No	Present when the call failed. Absent on success.
`entries`	No	Docket entries for this page (fixed at 20 per page; entries_page_size is not honored by upstream).
`court_id`	No	Court identifier — the stable value for filtering.
`case_name`	No	Short case name.
`docket_id`	No	Docket ID.
`date_filed`	No	Date the case was filed.
`assigned_to`	No	Assigned judge name; null if not recorded.
`jury_demand`	No	Jury demand status.
`next_cursor`	No	Next page number to pass as the `entries_page` argument (docket entries are page-paginated); null when this is the last page.
`referred_to`	No	Referred judge name; null if not recorded.
`entries_page`	No	Current entries page number (1-indexed).
`docket_number`	No	Docket number.
`pacer_case_id`	No	PACER case ID; null if not in RECAP.
`total_entries`	No	Total number of docket entries available — may exceed the returned entries list.
`case_name_full`	No	Full case name.
`date_terminated`	No	Date the case was terminated; null if active.
`jurisdiction_type`	No	Jurisdiction type.

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds real value beyond that: entries carry a document availability status, is_available=true means a RECAP-stored copy exists, and otherwise a PACER account is required — a meaningful auth/access constraint an agent would not otherwise know.

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 tightly-packed sentences with no filler, front-loaded with purpose then return content then the availability caveat. Every sentence carries distinct information.

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?

An output schema exists, so return-value detail is not required here; the description covers what is fetched, the availability semantics of the returned entries, and where the required ID comes from. Nothing an agent needs in order to call this correctly is missing.

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% and the schema already documents docket_id sourcing, entries_page pagination, and the ignored entries_page_size caveat. The description only restates the docket ID provenance, adding no syntax or format detail beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('Fetch full docket metadata and entry list') plus an explicit scope ('a single federal case by docket ID'). This clearly separates it from siblings like courtlistener_get_opinion and courtlistener_get_parties without requiring the schema to be opened.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly routes the agent for the prerequisite input: 'Obtain docket IDs from courtlistener_search_dockets or from opinion results.' That is clear when-to-use context, but it gives no exclusions or guidance on when a different get_* tool is preferable for a given case detail.

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

courtlistener_get_financial_disclosureGet Financial DisclosureA

Read-onlyIdempotent

Inspect

Fetch a single judicial financial disclosure by ID with its parsed line-item rows — investments, debts, positions, reimbursements, non-investment and spouse income, agreements, and gifts. This is the itemized companion to courtlistener_search_financial_disclosures (which returns only category counts). Pass categories:[...] to select specific categories; omit for all. Coded value/income columns are decoded to readable dollar ranges. When the full itemization is too large to inline, the response lists each category as a retrievable section by byte size while keeping the filing metadata and counts — re-call with categories:[...] to pull specific categories in full. Obtain disclosure IDs from courtlistener_search_financial_disclosures (the disclosure_id field).

ParametersJSON Schema

Name	Required	Description	Default
`categories`	No	Line-item categories to return in full: investments, debts, positions, reimbursements, non_investment_incomes, spouse_incomes, agreements, gifts. Omit for all categories (or an outline if they overflow the inline budget). Also the re-call selector — after an outline response, re-call with the category names it lists.
`disclosure_id`	Yes	Financial disclosure ID — the disclosure_id field from a courtlistener_search_financial_disclosures result.

Output Schema

ParametersJSON Schema

Name	Required	Description
`kind`	No	'full' returns the requested category rows; 'outline' lists each category as a retrievable section (by byte size) when the itemization overflows the inline budget. Filing metadata and counts are present either way.
`year`	No	Filing year.
`debts`	No	Debts and liabilities.
`error`	No	Present when the call failed. Absent on success.
`gifts`	No	Reported gifts.
`counts`	No	Count of line items in each disclosure category.
`pdf_url`	No	URL to the source disclosure PDF; null if unavailable.
`sections`	No	Retrievable categories, largest first — pass names to `categories` on a re-call.
`person_id`	No	Person ID of the filer — pass to courtlistener_get_judge; null if absent.
`positions`	No	Outside positions.
`agreements`	No	Continuing agreements.
`is_amended`	No	True if this filing is an amendment.
`page_count`	No	Page count of the source filing; null if not recorded.
`investments`	No	Investment holdings.
`report_type`	No	Report type (Nomination, Initial, Annual, Final, or Unknown).
`disclosure_id`	No	Financial disclosure ID.
`reimbursements`	No	Reimbursements.
`spouse_incomes`	No	Spouse income sources.
`retrieval_notice`	No	How to re-call the tool for specific categories when the itemization overflows.
`has_been_extracted`	No	True if line items were parsed from the PDF; category arrays are empty when false.
`non_investment_incomes`	No	Non-investment income sources.

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, yet the description adds substantial behavior beyond them: coded value/income columns are decoded into readable dollar ranges, oversized itemizations degrade to an outline of per-category byte sizes while preserving metadata and counts, and the outline triggers a documented re-call pattern. That overflow/decoding behavior is exactly the kind of trait annotations cannot express.

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 a single dense paragraph that front-loads the core action and then layers the overflow caveat and ID provenance. Every sentence carries information, though the amount of detail (decoding, outline sizes, re-call) makes it longer than a minimal definition would need.

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?

An output schema exists so return values need not be enumerated, and the description still supplies the two things an agent most needs that the schema lacks: the decoded-value behavior and the outline/re-call fallback for large filings. Given a 2-parameter tool with full schema coverage and annotations, this is complete.

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?

Schema coverage is 100%, so the baseline is 3 and the schema already documents both parameters. The description nonetheless adds meaning the schema does not fully carry: the categories parameter doubles as the re-call selector after an outline, and omitting it can yield an outline rather than everything — a subtlety worth flagging. It does not add syntax or format detail beyond that.

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?

States a specific verb and resource ('Fetch a single judicial financial disclosure by ID') plus the exact payload ('parsed line-item rows — investments, debts, positions...'). It explicitly names the sibling it complements and how it differs ('courtlistener_search_financial_disclosures (which returns only category counts)'), so an agent can route between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use routing versus the search sibling, tells the agent how to obtain the required ID ('the disclosure_id field'), and specifies the omission default for categories. It also covers the non-obvious re-call workflow after an outline response, which is genuine usage guidance rather than restatement.

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

courtlistener_get_judgeGet Judge ProfileA

Read-onlyIdempotent

Inspect

Fetch full biographical profile for a single judge: positions on record — judicial appointments across all courts plus non-judicial roles — education, political affiliations, and ABA ratings. The position list is paginated upstream and walked under a page bound; the response reports whether it was truncated. Obtain person IDs from courtlistener_search_judges results.

ParametersJSON Schema

Name	Required	Description	Default
`person_id`	Yes	Judge person ID from a search result's person_id field. Identifies a specific judge across all courts they have served on.

Output Schema

ParametersJSON Schema

Name	Required	Description
`dob`	No	Date of birth as CourtListener stores it, always full ISO 8601 — but the month and day are placeholders unless dob_granularity is "day". Read dob_granularity before presenting this as an exact date. Null if not recorded.
`dod`	No	Date of death as CourtListener stores it, always full ISO 8601 — precision qualified by dod_granularity, as with dob. Null if living or not recorded.
`name`	No	Full name.
`error`	No	Present when the call failed. Absent on success.
`fjc_id`	No	Federal Judicial Center ID for cross-referencing with FJC data; null if not available.
`gender`	No	Gender.
`notice`	No	Present only when positions[] was truncated: what was withheld.
`dob_city`	No	City of birth; null if not recorded.
`dob_state`	No	State of birth; null if not recorded.
`education`	No	Educational history.
`person_id`	No	Person ID.
`positions`	No	Positions on record, across all courts — judicial appointments plus non-judicial roles (private practice, prosecutor, professor), which carry no court and describe themselves in job_title. CourtListener paginates this list and the walk is bounded, so read the truncated flag before treating it as a complete career.
`truncated`	No	True when the bounded /positions/ page walk stopped with pages outstanding — positions[] is then a prefix of the person's record, not the whole of it. False when the walk reached the end.
`aba_ratings`	No	ABA qualification ratings, expanded to readable labels (e.g., "Well Qualified").
`positionsShown`	No	Number of position records returned.
`dob_granularity`	No	Precision actually recorded for dob: "year", "month", or "day". Null when CourtListener recorded no precision. An unrecognized upstream value passes through unchanged.
`dod_granularity`	No	Precision actually recorded for dod: "year", "month", or "day". Null when CourtListener recorded no precision.
`political_affiliations`	No	Political affiliation history.

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly and idempotent. The description adds genuinely useful behavior: the position list is paginated upstream, walked under a page bound, and the response reports whether it was truncated. That is real context beyond the annotations.

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 sentences, front-loaded with the content listing, followed by the pagination caveat and the ID provenance. No filler.

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?

With an output schema present, return values need no explanation; the description still flags truncation reporting, which is the one behavioral nuance an agent needs. Nothing material is missing for a single-parameter read tool.

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% and the single person_id is fully documented in the schema, including its provenance. The description's pointer to search results mostly repeats the schema, so baseline 3 is correct.

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?

States a specific verb (Fetch) and resource (full biographical profile for a single judge), then enumerates the contents: positions, education, political affiliations, ABA ratings. An agent can distinguish this from courtlistener_search_judges immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly routes the agent to courtlistener_search_judges as the source of person IDs, which is the key prerequisite. It does not state any when-not condition or alternative retrieval paths, so it falls short of a 5.

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

courtlistener_get_opinionGet Court OpinionA

Read-onlyIdempotent

Inspect

Fetch the full text and metadata for a single opinion cluster by cluster ID. A cluster groups all opinions filed in a case — majority, concurrence, dissent, and per curiam. Returns the cluster metadata (case name, court, citations, dates) plus every opinion variant with HTML and plain text. When the combined opinion text is too large to inline, the response lists each variant as a retrievable section (opinion_) while keeping the cheap cluster metadata — re-call with sections:[...] to pull specific variants in full. Obtain cluster IDs from courtlistener_search_opinions, courtlistener_lookup_citation, or docket results.

ParametersJSON Schema

Name	Required	Description	Default
`sections`	No	Opinion variant identifiers to retrieve in full, from a prior outline response (e.g. ["opinion_12345"]). Omit to return all variants, or an outline if they overflow the inline byte budget.
`cluster_id`	Yes	Opinion cluster ID — identifies a case decision and groups all opinion variants (majority, concurrence, dissent). Obtain from courtlistener_search_opinions, courtlistener_lookup_citation, or from docket results that link to opinions.

Output Schema

ParametersJSON Schema

Name	Required	Description
`kind`	No	'full' returns the opinion variants (all, or a selected subset); 'outline' lists each variant as a retrievable section (opinion_<id>) when the opinions overflow the inline byte budget. Cluster metadata is present either way.
`court`	No	Court display name.
`error`	No	Present when the call failed. Absent on success.
`judges`	No	Judge names.
`posture`	No	Procedural posture (may be empty).
`court_id`	No	Court identifier.
`opinions`	No	All opinion variants within this cluster. Present in full mode; omitted in outline mode — re-call with sections:["opinion_<id>"] to retrieve specific variants.
`sections`	No	Retrievable opinion variants, largest first — pass names to `sections` on a re-call.
`syllabus`	No	Syllabus text (may be empty).
`case_name`	No	Short case name.
`citations`	No	All known citation strings for this case.
`docket_id`	No	Associated docket ID.
`cite_count`	No	Total number of citations from other opinions.
`cluster_id`	No	Opinion cluster ID.
`date_filed`	No	Date the opinion was filed.
`docket_number`	No	Docket number.
`case_name_full`	No	Full case name with parties.
`retrieval_notice`	No	How to re-call the tool for specific opinion variants when the opinions overflow.
`precedential_status`	No	Publication/precedential status.

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, yet the description adds substantial behavior beyond them: the overflow handling (large text degrades to retrievable opinion_<id> sections while keeping cheap cluster metadata) and the re-call-with-sections pattern. That is exactly the kind of dynamic behavior an agent cannot infer from annotations or schema.

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 sentences, each load-bearing: purpose, cluster definition, return payload, overflow/re-call, ID sourcing. Slightly dense and the cluster definition mildly overlaps with the schema's cluster_id description, but it is front-loaded and free of filler.

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 two-parameter read tool with an output schema already present, the description covers purpose, ID sourcing, overflow behavior, and retrieval flow. Nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by explaining the relationship between the two parameters — how sections interacts with an overflowed outline and when to omit it — beyond the field-level schema text.

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?

States a specific verb (fetch) and resource (a single opinion cluster by cluster ID), and immediately disambiguates by defining what a cluster is. An agent can tell this apart from the sibling search/lookup tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Clearly frames this as the single-item retrieval path and names three concrete sources for the required cluster ID (courtlistener_search_opinions, courtlistener_lookup_citation, docket results). It lacks an explicit 'do not use for X' exclusion, but the use context is unambiguous.

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

courtlistener_get_oral_argumentGet Oral ArgumentA

Read-onlyIdempotent

Inspect

Fetch the full detail record for a single oral argument audio recording by its ID (the audio_id from courtlistener_search_oral_arguments). Returns the case name, panel judge IDs, duration, MP3 download URL, linked docket, and the speech-to-text transcript when transcription has completed. A long transcript is withheld and listed as a retrievable section instead; re-call with sections:["transcript"] to pull it. Every other field is present either way. The argument date is not on this record — it comes from the search result or the linked docket.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	Audio recording ID — the audio_id field from a courtlistener_search_oral_arguments result.
`sections`	No	Section identifiers to retrieve, from a prior outline response — ["transcript"] is the only one that adds anything, since every other field is returned regardless. A selection that omits "transcript" therefore returns the record without it. Omit this argument entirely for the whole record, or the record minus an oversized transcript.

Output Schema

ParametersJSON Schema

Name	Required	Description
`kind`	No	'full' carries the transcript inline; 'outline' withholds it and lists it as a retrievable section because it overflows the inline byte budget. Every other field of the record is present either way.
`error`	No	Present when the call failed. Absent on success.
`judges`	No	Free-text judge names; often empty on this endpoint.
`sections`	No	Sections withheld from this response — only ever `transcript`; pass its name to `sections` on a re-call. Absent when nothing was withheld.
`case_name`	No	Case name.
`docket_id`	No	Associated docket ID; 0 if not linked.
`panel_ids`	No	Person IDs of panel judges — pass to courtlistener_get_judge.
`transcript`	No	Speech-to-text transcript; empty string if transcription has not completed. The only field an outline response withholds — re-call with sections:["transcript"] to retrieve it.
`download_url`	No	Direct MP3 download URL; null if not available.
`case_name_full`	No	Full case name with parties.
`has_transcript`	No	True if a speech-to-text transcript is available.
`duration_seconds`	No	Recording duration in seconds.
`oral_argument_id`	No	Audio recording ID.
`retrieval_notice`	No	How to re-call the tool for the transcript when it overflows the inline budget.

TDQS

A4.5/5.0

Behavior5/5

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

With annotations only declaring readOnlyHint and idempotentHint, the description carries the interesting behavior: it enumerates returned fields, discloses the transcript-withholding rule for long transcripts, and gives the recovery action. This is substantive disclosure well beyond the safety hints.

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?

Front-loaded with the primary action, then returns, then the transcript edge case, then the date caveat. Every sentence contributes a non-obvious fact (withholding rule, re-call syntax, field ownership of the date).

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?

Annotations cover the safety profile and an output schema exists, so the description is not obliged to detail returns, yet it still names the key fields and the transcript carve-out. Nothing essential to a correct call is missing.

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% and the schema's own description already explains that sections:["transcript"] is the only meaningful value and that omitting it returns the record minus an oversized transcript. The description largely restates this, adding little beyond what the structured field already provides.

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?

States a specific verb ('Fetch the full detail record') and resource ('a single oral argument audio recording by its ID'), scoping itself clearly against the search sibling by naming the exact source field (audio_id from courtlistener_search_oral_arguments). An agent can distinguish it from the search and get_* siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Establishes the entry condition (the audio_id from search_oral_arguments) and the re-call path with sections:["transcript"] when a transcript is withheld. It also disambiguates where the argument date lives (search result or linked docket). It lacks an explicit when-not-to-use statement, but the context is clear.

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

courtlistener_get_partiesGet PartiesA

Read-onlyIdempotent

Inspect

Fetch all parties and attorneys of record for a RECAP federal docket by docket ID. Returns each party's name, role (Plaintiff, Defendant, Petitioner, Respondent, etc.), and their attorneys with contact information, scoped to this docket. Costs two upstream requests per call (parties + attorney lookup) against a rate-limited free tier, and one more for each extra page of a large attorney roster. Obtain docket IDs from courtlistener_search_dockets or courtlistener_get_docket.

ParametersJSON Schema

Name	Required	Description
`cursor`	No	Pagination cursor from a previous response's next_cursor field. Omit for the first page. This is an opaque token, not a page number — CourtListener cursor-paginates this endpoint, so a numeric value selects nothing and re-serves the first page.
`docket_id`	Yes	Docket ID from a courtlistener_search_dockets or courtlistener_get_docket result's docket_id field.
`page_size`	No	Requested number of parties per page (1–10). CourtListener paginates this endpoint at a fixed size and does not honor the requested value, so a page can come back larger than asked for.

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`parties`	No	Parties on this page.
`docket_id`	No	Docket ID these parties belong to.
`totalCount`	No	Total parties on this docket across all pages — this endpoint reports its count as a URL rather than a number, so the total is only derivable when the first page is also the last, and is absent for any list spanning more than one page.
`next_cursor`	No	Opaque pagination cursor for the next page — pass it back as the `cursor` argument; null when this is the last page.
`total_parties`	No	Total parties on this docket across all pages; null when no total is derivable — CourtListener serves the count as a URL rather than a number here, so it is only known when the first page is also the last.

TDQS

A4.4/5.0

Behavior5/5

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

Annotations cover readOnlyHint and idempotentHint, and the description adds substantial extra context: the cost model (two upstream requests per call plus one per extra page), the rate-limited free tier, and the return shape (name, role, attorneys with contact info). This is exactly the value-behind-annotations that earns a high score.

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?

Three tightly written sentences, front-loaded with the core purpose followed by return contents, cost, and ID sourcing. The return-field enumeration is slightly redundant given the output schema, but each sentence carries actionable content.

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?

An output schema exists so return values need no explanation, yet the description still summarizes them alongside cost and ID provenance. For a read-only lookup tool, nothing an agent needs to call it correctly is missing.

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 the schema already documents cursor, docket_id, and page_size in detail. The description only reinforces the docket_id sourcing, adding little parameter meaning beyond what the schema provides; baseline 3 applies.

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?

States a specific verb and resource ('Fetch all parties and attorneys of record for a RECAP federal docket by docket ID') and enumerates the returned fields, making it clearly distinguishable from siblings like courtlistener_get_docket. An agent can identify what it retrieves and its scope without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly routes the agent to courtlistener_search_dockets or courtlistener_get_docket to obtain the required docket_id, giving clear context for when this tool applies. It does not state when NOT to use it, but the RECAP-docket scoping is a strong implied boundary.

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

courtlistener_lookup_citationLookup Legal CitationA

Read-onlyIdempotent

Inspect

Resolve legal citations (e.g., "410 U.S. 113", "93 S. Ct. 705") to opinion cluster IDs and case metadata. Enables workflows that start from a known citation rather than a search query. CourtListener extracts every citation it finds in the submitted text, so passing a passage returns one entry per citation, each with its own resolution status — an unresolved or ambiguous citation is reported in the results, not raised as an error. Supports standard US reporter formats. Costs one request against CourtListener's per-citation quota, plus one ordinary request per distinct docket whose court is resolved — max_court_lookups bounds that second half (default 4, set 0 to skip court resolution entirely). CourtListener meters this endpoint by citations submitted rather than by call, so a long passage spends proportionally more of that quota. Requires authentication — uses the CourtListener /citation-lookup/ endpoint.

ParametersJSON Schema

Name	Required	Description	Default
`citation`	Yes	Text to extract citations from — normally a single citation (e.g., "410 U.S. 113", "347 U.S. 483", "93 S. Ct. 705"), but any passage works and every citation in it is resolved. Supports standard reporter formats. Up to 64000 characters, which is CourtListener's own ceiling; a longer passage is rejected here rather than spending a request to be refused upstream.
`max_court_lookups`	No	How many distinct dockets this call may spend a request on to resolve cluster courts. The lookup itself is metered separately by CourtListener (per citation submitted), so this budget is drawn entirely from the ordinary per-request allowance — published free tier 5/min, 50/hour, 125/day, varying by token tier. 0 skips court resolution and costs nothing beyond the lookup; 20 is the ceiling. Clusters past the budget come back with court null and court_resolution "over_budget".

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Caveats on this result: a recovery hint when no citation in the input resolved to a case, and counts of the clusters whose court went unresolved — split by whether the per-call docket budget ran out or an attempted lookup returned nothing, since only the first is worth retrying with a larger budget. Absent when none applies.
`matches`	No	One entry per citation CourtListener extracted from the input, in the order they appear.
`queriedCitation`	No	The citation string that was looked up.

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: discloses per-citation quota metering, the additional per-docket request cost, the 64000-char ceiling, the authentication requirement, and the key behavioral trait that unresolved/ambiguous citations are returned in results rather than raised as errors.

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?

Front-loads the purpose and input examples, then layers cost/auth/limit details in a single dense block. Every sentence carries load, though the quota discussion is somewhat thick and could be tightened.

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?

An output schema exists so return-value documentation is unnecessary, and the description covers the remaining gaps an agent needs: auth, meter model, budget semantics, size limit, and partial-failure handling.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: it clarifies that the quota is charged per citation submitted rather than per call (so a long passage costs more) and that max_court_lookups draws on the separate per-request allowance with clusters past budget returning court_resolution "over_budget".

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?

States a specific verb+resource ("Resolve legal citations ... to opinion cluster IDs and case metadata") and gives concrete input examples. It also distinguishes itself from the search siblings by naming the workflow it serves: "start from a known citation rather than a search query."

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Clearly frames the selection context (citation-first workflows vs. query-first search) and explains the max_court_lookups budget trade-off, including setting 0 to skip court resolution. It stops short of naming a specific sibling alternative the way the calibration's top example does.

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

courtlistener_lookup_courtsLookup CourtsA

Read-only

Inspect

List courts with optional filtering by jurisdiction type, active/inactive status, and scraper coverage. Primarily used to discover court IDs for use in search and filter parameters across all other courtlistener tools. Defaults to the active bench — the courts CourtListener still scrapes; pass status:'inactive' for historical courts or status:'any' for every court. A bundled snapshot returns the complete list of matching court IDs without paging whenever the filtered set fits the response budget, which covers the default bench and every jurisdiction filter. Full court records — names, citation strings, scraper status — come live from CourtListener at a fixed 20 rows per page, so pull those only when a court ID alone is not enough.

ParametersJSON Schema

Name	Required	Description	Default
`page`	No	Page number (1-indexed). CourtListener serves /courts/ at a fixed 20 rows per page and ignores any requested page size, so the number of pages is the enrichment totalCount divided by 20 — there is no way to pull a larger page. Pass the next_cursor from a previous response here to walk them one call at a time.
`status`	No	Which bench to return. 'active' (default) returns only courts CourtListener currently scrapes; 'inactive' returns only the historical and defunct courts it no longer scrapes; 'any' returns both. The two filtered sets are disjoint, so 'any' is the only value that reaches the whole list — but reaching all of it means paging, one call per 20 courts, and the inactive bench is several times larger than the active one. Prefer the narrowest value that answers the question, and narrow with jurisdiction rather than paging the full list.	active
`jurisdiction`	No	Jurisdiction type — CourtListener's own court classification, one code per court: F=Federal Appellate, FD=Federal District, FB=Federal Bankruptcy, FBP=Federal Bankruptcy Panel, FS=Federal Special, S=State Supreme, SA=State Appellate, ST=State Trial, SS=State Special, SAG=State Attorney General, TRS=Tribal Supreme, TRA=Tribal Appellate, TRT=Tribal Trial, TRX=Tribal Special, TS=Territory Supreme, TA=Territory Appellate, TT=Territory Trial, TSP=Territory Special, MA=Military Appellate, MT=Military Trial, C=Committee, I=International. Omit to list all. SCOTUS and the numbered circuits are F; USITC and FISC are FS. Upstream's Testing code is not offered here: /courts/ excludes testing courts from every response, so a filter on it can only ever return nothing. Accepted but matching no court as of the 2026-07-30 snapshot: TSP, MT. Courts whose stored jurisdiction is not one of these codes (njcirctsussex, ohctapp1) are unreachable through this filter at any value — the value they store is not one the filter accepts. Pass those ids straight to the tool that needs them, or list with no jurisdiction filter.
`has_opinion_scraper`	No	Filter to courts with active opinion scraping. Useful when planning search queries — courts without scrapers have sparse coverage.

Output Schema

ParametersJSON Schema

Name	Required	Description
`page`	No	Current page number (1-indexed).
`error`	No	Present when the call failed. Absent on success.
`courts`	No	Matching courts on this page.
`notice`	No	Recovery hint when no courts match the applied filters.
`totalCount`	No	Total courts returned.
`next_cursor`	No	Next page number to pass as the `page` argument (this list is page-paginated at a fixed 20 rows/page); null when this is the last page — a non-null value means the courts shown are a partial view of the filtered set.
`all_matching_court_ids`	No	Every court id matching the same filters, from a snapshot of /courts/ bundled with this server (taken 2026-07-30) — the complete set, not just this page, and free of any request. Paging `courts` is only needed for the fields a court id alone does not carry (full_name, citation_string, scraper flags). Empty when more than 1000 courts match, since a prefix of the set would be indistinguishable from the whole of it — check all_matching_court_ids_complete before reading emptiness as "no courts match". A court added or retired upstream since the snapshot date appears in `courts` but may be missing here.
`all_matching_court_ids_complete`	No	True when all_matching_court_ids holds every matching court id. False when more than 1000 courts match: the list is withheld whole rather than truncated, and the notice gives the count and how to narrow.

TDQS

A4.4/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), but the description adds genuinely non-obvious behavior: a bundled snapshot serves the complete matching ID list without paging when the set fits the response budget, whereas full records come live from CourtListener at a fixed 20 rows per page. That paging/response-budget distinction is not derivable from the annotations and materially affects how an agent plans calls. Minor overlap with the schema's page description 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.

Conciseness4/5

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

Front-loaded with purpose and the ID-discovery rationale, then the status defaults, then the paging/snapshot economics — a sensible ordering with no filler sentences. It is slightly long and repeats the '20 rows per page' constraint already stated in the page parameter description, which costs it a point.

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?

An output schema exists, so return values need not be explained. The description covers the remaining complexity an agent needs: default scope, disjoint status benches, filter narrowing, and the snapshot-vs-live paging tradeoff. Nothing required to call this four-parameter, zero-required-parameter tool correctly is missing.

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%, and the schema already documents status semantics and the full jurisdiction code map in more detail than the description. The description largely restates the defaults ('defaults to the active bench', status:'inactive'/'any') rather than adding new parameter meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('List courts') and immediately scopes it with the available filters (jurisdiction, status, scraper coverage). It also explicitly positions itself against the rest of the toolset: 'Primarily used to discover court IDs for use in search and filter parameters across all other courtlistener tools.' An agent can tell this is the ID-discovery tool rather than any of the get_/search_ siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use and when-not guidance: default is the active bench, pass status:'inactive' for historical courts, status:'any' for everything, and 'pull those only when a court ID alone is not enough.' It also directs the agent to prefer the narrowest filter and to narrow with jurisdiction rather than page the full list, which is a concrete routing rule.

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

courtlistener_search_docketsSearch Federal Court DocketsA

Read-only

Inspect

Search RECAP federal court dockets. Query terms match case name, docket number, party, and attorney names; filters narrow by party name, court, and filing date. RECAP is a crowd-sourced mirror of PACER (the federal court filing system) — coverage varies by court and date. Returns docket metadata with the parties, attorneys, and firms of record, plus up to 3 sample document entries per docket. Use courtlistener_lookup_courts to find court IDs.

ParametersJSON Schema

Name	Required	Description
`q`	Yes	Query terms matched against case name, docket number, party names, and attorney names. Example: "Apple Inc patent infringement".
`court`	No	Filter to a specific federal court ID (e.g., "dnd", "cacd", "deb" for Delaware Bankruptcy). Use courtlistener_lookup_courts to find court IDs.
`cursor`	No	Pagination cursor from a previous response's next_cursor field.
`page_size`	No	Number of results to request (default 20). CourtListener search enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results.
`party_name`	No	Filter to dockets listing a specific party by name — applied in addition to (AND with) the q query. More precise than including party names in q when the party name is known.
`filed_after`	No	Earliest case filing date (ISO 8601).
`filed_before`	No	Latest case filing date (ISO 8601).

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Recovery hint when results are empty — echoes filters and suggests how to broaden.
`results`	No	Matching docket records.
`totalCount`	No	Total matching dockets.
`next_cursor`	No	Pagination cursor for the next page; null when no more results.
`coverage_note`	No	Note about RECAP coverage limitations.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly, openWorld, non-idempotent), so the bar is lower. The description still adds valuable non-obvious context: RECAP is a crowd-sourced PACER mirror with variable court/date coverage, and results include parties, attorneys, firms, plus up to 3 sample documents per docket. Rate limits and odd pagination behavior are left to the schema.

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?

Four compact sentences, front-loaded with the core action, then matching semantics, then the coverage caveat, then the cross-tool pointer. Every sentence carries distinct information with no filler.

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 7-parameter search with a fully documented schema and an output schema, the description supplies everything an agent needs: what is searched, how filters interact, the RECAP coverage caveat, and where to obtain court IDs. Return values are already covered by the output schema.

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?

Schema coverage is 100%, so baseline is 3. The description goes beyond the schema by articulating the division of labor: q is a broad term match across case name/number/parties/attorneys, while party_name/court/filed dates are narrowing filters. That conceptual framing helps an agent choose between q and party_name.

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?

States a specific verb and resource ('Search RECAP federal court dockets') and immediately scopes what query terms match and what filters exist. It is clearly distinguishable from sibling tools like get_docket (retrieval) and search_opinions/search_judges (other resources).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It tells the agent when this search is appropriate (full-text docket search with narrowing filters), clarifies that q vs party_name combine as AND, and routes the agent to courtlistener_lookup_courts for court IDs. There is no explicit 'when not to use' or comparison against other search_* siblings, which keeps it from a 5.

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

courtlistener_search_financial_disclosuresSearch Financial DisclosuresA

Read-only

Inspect

Search federal judicial financial disclosure filings — the annual reports judges file on investments, gifts, debts, outside positions, and income. Filter by judge (person ID from courtlistener_search_judges) and/or filing year; the year filter is applied to the fetched page only (CourtListener has no server-side year filter), so page through with cursor to reach a judge's filings for a year that fall on later pages. Returns per-filing metadata, category counts, itemized gifts, and a link to the source PDF. Line-item investments (often hundreds per filing, with coded values) are summarized as counts; the linked PDF carries the full itemization. Use this for judicial-ethics and recusal research after identifying a judge's person ID.

ParametersJSON Schema

Name	Required	Description
`year`	No	Filing year to filter by (e.g., 2022). Applied client-side to the fetched page only — CourtListener rejects a server-side year param, so filings for this year on later pages are not included. When a page has no match for the year but more pages remain, next_cursor is returned; pass it as cursor to check the next page. Omit to return all years on the page.
`cursor`	No	Pagination cursor from a previous response's next_cursor field.
`judge_id`	No	Person ID of the judge whose disclosures to return — obtain from courtlistener_search_judges (the person_id field). Omit to browse across all filers.
`page_size`	No	Number of filings to request (default 20). CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 filings.

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Recovery hint when no filings are found — echoes filters and suggests next steps.
`results`	No	Matching financial disclosure filings.
`totalCount`	No	Total matching disclosure filings — present only when the API reports a numeric count (this endpoint returns it as a URL by default, so it is usually absent).
`next_cursor`	No	Pagination cursor for the next page; null when no more results.

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare readOnlyHint/openWorldHint, so the safety profile is covered; the description adds genuinely non-obvious behavior: the year filter is client-side only, so later pages may hold matching filings and the agent must page with cursor. It also discloses that line-item investments are returned as counts with the PDF carrying full itemization. This is well beyond what the annotations provide.

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?

Dense but front-loaded: the resource definition leads, followed by filtering options, the critical pagination caveat, return shape, and use case. A few sentences (e.g., the line-item/PDF note, the year-filter mechanics) duplicate the schema, but nothing is wasted enough to hurt.

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?

An output schema exists, so return values need not be fully described, yet the description still usefully characterizes the response (metadata, category counts, itemized gifts, PDF link). Combined with the pagination and filtering caveats, an agent has enough to call it correctly; only the search-vs-get routing is left implicit.

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 is already documented in the schema, including the same client-side-year and minimum-page-size caveats. The description restates the judge_id source and year behavior, adding only marginal value over the schema baseline.

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?

States a specific verb (Search) and resource (federal judicial financial disclosure filings) and immediately scopes it with the content types it covers (investments, gifts, debts, outside positions, income). An agent can distinguish this search tool from the sibling courtlistener_get_financial_disclosure without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly names the use case ('judicial-ethics and recusal research') and the prerequisite ('after identifying a judge's person ID'), routing the agent to courtlistener_search_judges for the ID. It does not, however, explicitly tell the agent when to prefer this search over the sibling courtlistener_get_financial_disclosure for a single filing.

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

courtlistener_search_judgesSearch JudgesA

Read-only

Inspect

Search judge/person records by name, appointing president, court, political affiliation, or demographic. Returns biographical data, current position, and appointment summary. Use courtlistener_get_judge for full appointment history and education records.

ParametersJSON Schema

Name	Required	Description
`q`	Yes	Search query — judge name, court, city, or relevant keywords.
`court`	No	Filter to judges who have held a position at this court (e.g., "scotus", "ca9"). Use court_id strings from courtlistener_lookup_courts.
`cursor`	No	Pagination cursor from a previous response's next_cursor field.
`appointer`	No	Filter by appointing president's last name (e.g., "Obama", "Trump", "Biden"). Matches against the appointer field in position records.
`page_size`	No	Number of results to request (default 20). CourtListener search enforces a minimum of 20 results per page regardless of the value passed.
`political_affiliation`	No	Filter by political affiliation: d=Democrat, r=Republican, i=Independent, l=Libertarian, g=Green Party, u=Unknown/unconfirmed. Based on party of the appointing president or election affiliation.

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Recovery hint when results are empty — echoes filters and suggests how to broaden.
`results`	No	Matching judge records.
`totalCount`	No	Total matching judge records.
`next_cursor`	No	Pagination cursor for the next page; null when no more results.

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds what the result set contains (biographical data, current position, appointment summary), but says nothing about pagination limits beyond the schema, rate limits, 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.

Conciseness5/5

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

Three short sentences with zero filler: capability first, then return shape, then the sibling escape hatch. Everything is front-loaded and each sentence earns its place.

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 an output schema present, the description need not explain return values, and it correctly leaves parameter details to the schema. It is complete enough to invoke the tool confidently, missing only edge-case guidance such as pagination behavior or result limits.

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%, including enum meanings for political_affiliation and the page_size caveat, so the schema does the heavy lifting. The description's mention of filter dimensions only restates what is already in the parameter descriptions, adding no new syntax or format guidance.

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?

States a specific verb (Search) and resource (judge/person records) and enumerates the filter dimensions — name, appointing president, court, political affiliation, demographic — which map directly to the input schema. It also distinguishes itself from the sibling retrieval tool courtlistener_get_judge.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly routes the agent to courtlistener_get_judge when full appointment history and education records are needed, which clarifies the search-vs-retrieve boundary. It lacks any statement of when this search is inappropriate (e.g., fetching a known judge by ID).

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

courtlistener_search_opinionsSearch Court OpinionsA

Read-only

Inspect

Full-text search across 9M+ written US court opinions with field-level filtering. Returns opinion cluster summaries with case metadata, citations, matched text snippets, and the individual opinion variants filed in each case. Supports CourtListener field syntax (caseName:"roe v wade", court_id:scotus, judge:"Alito") and boolean operators (AND, OR, NOT). Use courtlistener_lookup_courts to find court IDs. CourtListener publishes free-tier limits of 5 req/min, 50/hr, 125/day; actual limits vary by token tier.

ParametersJSON Schema

Name	Required	Description	Default
`q`	Yes	Full-text query. Supports field syntax (caseName:"roe v wade", court_id:scotus, judge:"Alito") and boolean operators (AND, OR, NOT). Use plain English for semantic-style queries or legal citations.
`court`	No	Filter to a specific court by court ID (e.g., "scotus", "ca9", "nyed"). Use courtlistener_lookup_courts to find court IDs.
`cursor`	No	Pagination cursor from a previous response's next_cursor field. Omit for the first page.
`status`	No	Opinion publication status. "Published": precedential. "Unpublished": not citable as precedent in most jurisdictions. "Errata": corrections. "Separate": separate opinion filed outside main cluster. "In-chambers": single-justice order. "Relating-to": companion or related-case order. Omit to search all statuses.
`order_by`	No	Result ordering. "score desc" (default) ranks by relevance. "citeCount desc" surfaces most-cited opinions first.	score desc
`page_size`	No	Number of results to request (default 20). CourtListener search enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results. Each search costs one request against the rate limit.
`filed_after`	No	Earliest filing date (ISO 8601, e.g., "2020-01-01"). Narrows search to opinions filed on or after this date.
`filed_before`	No	Latest filing date (ISO 8601). Narrows search to opinions filed before or on this date.

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Recovery hint when results are empty — echoes filters and suggests how to broaden.
`results`	No	Matching opinion cluster summaries.
`totalCount`	No	Total matching opinions in the corpus.
`next_cursor`	No	Pagination cursor for the next page; null when no more results.
`effectiveQuery`	No	Query terms sent to CourtListener.

TDQS

A4.5/5.0

Behavior5/5

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

Annotations cover read-only/open-world, but the description adds substantial context beyond them: the concrete return shape (opinion cluster summaries, case metadata, citations, snippets, individual opinion variants) and the published free-tier rate limits (5/min, 50/hr, 125/day) with a note that limits vary by token tier. This is exactly the operational detail annotations cannot express.

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?

Four dense sentences, front-loaded with what the tool does, then return shape, query syntax, sibling helper, and limits. No filler; every sentence carries information an agent needs.

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 an 8-parameter open-world search tool with an output schema, the description covers purpose, return shape, query syntax, the court-ID helper, pagination via cursor, and rate limits. Nothing required to call it correctly is missing.

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 the schema already documents all eight parameters in detail; the description's field-syntax and boolean-operator guidance largely duplicates the q parameter's own description. Baseline 3 is appropriate since the description adds little meaning beyond the schema.

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?

States a specific verb and resource ('Full-text search across 9M+ written US court opinions') plus scope ('field-level filtering') and scale. An agent can distinguish it from siblings like courtlistener_search_dockets or courtlistener_get_opinion from the description alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear context for use (full-text/field-filtered discovery) and explicitly routes to courtlistener_lookup_courts for court IDs. It does not state when to prefer this over sibling search tools (e.g., search_dockets) or when not to use it, so it stops short of full when/when-not guidance.

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

courtlistener_search_oral_argumentsSearch Oral ArgumentsA

Read-only

Inspect

Search appellate oral argument audio recordings — the largest public collection of oral argument audio. Returns recording metadata with two direct MP3 links per result (download_url at the originating court, local_path for CourtListener's durable copy), panel judge IDs, and transcript snippets where available. Panel judge IDs can be passed to courtlistener_get_judge for biographical context.

ParametersJSON Schema

Name	Required	Description
`q`	Yes	Query terms matched against case name and transcribed argument text (where available).
`court`	No	Filter to a specific court (e.g., "scotus", "ca9").
`cursor`	No	Pagination cursor from a previous response's next_cursor field.
`page_size`	No	Number of results to request (default 20). CourtListener search enforces a minimum of 20 results per page regardless of the value passed.
`argued_after`	No	Earliest date the case was argued (ISO 8601) — filters by argument date, not publication date.
`argued_before`	No	Latest date the case was argued (ISO 8601).

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Recovery hint when results are empty — echoes filters and suggests how to broaden.
`results`	No	Matching oral argument recordings.
`totalCount`	No	Total matching oral argument recordings.
`next_cursor`	No	Pagination cursor for the next page; null when no more results.

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds useful behavioral texture (two distinct MP3 links, transcript snippets only 'where available') but it is largely return-shape detail rather than constraints, auth needs, or rate limits.

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?

Three front-loaded sentences: purpose first, then return contents, then the follow-up workflow. Efficient, though the enumeration of return fields is slightly padded given an output schema exists.

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 search tool with full schema coverage, annotations, and an output schema, nothing critical is missing. The remaining gap — pagination/result-cap behavior and when to choose this over sibling search tools — is minor.

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 is already documented — including the query semantics, court codes, cursor pagination, and the argued_after/argued_before date distinction. The description adds nothing param-specific beyond that, so the baseline 3 applies.

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?

States a specific verb (Search) and resource (appellate oral argument audio recordings) and scopes it with 'the largest public collection.' It is clearly separable from the sibling courtlistener_get_oral_argument (fetch one) and from search_opinions/search_dockets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives clear context for use — free-text query against case name and transcript — and routes the agent onward by noting panel judge IDs can be passed to courtlistener_get_judge. It does not, however, state when to prefer this over courtlistener_get_oral_argument or search_opinions.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

4 tool updatesSep 30, 2026

Changedcourtlistener_search_dockets2 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_query`: CourtListener rejects caller-authored query or filter syntax with a recognized diagnostic. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."

changedOutput schema / properties / error / properties / data / properties / reason / examples

Previous value: -[
-  "rate_limited",
-  "empty_query",
-  "invalid_date"
-]New value: +[
+  "invalid_query",
+  "rate_limited",
+  "empty_query",
+  "invalid_date"
+]

Changedcourtlistener_search_judges2 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_query`: CourtListener rejects caller-authored query or filter syntax with a recognized diagnostic. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. Other values are possible when a failure originates below the handler."

changedOutput schema / properties / error / properties / data / properties / reason / examples

Previous value: -[
-  "rate_limited",
-  "empty_query"
-]New value: +[
+  "invalid_query",
+  "rate_limited",
+  "empty_query"
+]

Changedcourtlistener_search_opinions2 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_query`: CourtListener rejects caller-authored query or filter syntax with a recognized diagnostic. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."

changedOutput schema / properties / error / properties / data / properties / reason / examples

Previous value: -[
-  "rate_limited",
-  "empty_query",
-  "invalid_date"
-]New value: +[
+  "invalid_query",
+  "rate_limited",
+  "empty_query",
+  "invalid_date"
+]

Changedcourtlistener_search_oral_arguments2 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: argued_after or argued_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_query`: CourtListener rejects caller-authored query or filter syntax with a recognized diagnostic. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: argued_after or argued_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."

changedOutput schema / properties / error / properties / data / properties / reason / examples

Previous value: -[
-  "rate_limited",
-  "empty_query",
-  "invalid_date"
-]New value: +[
+  "invalid_query",
+  "rate_limited",
+  "empty_query",
+  "invalid_date"
+]

14 tool updatesSep 29, 2026

Changedcourtlistener_get_citations3 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. Both directions resolve the source cluster before searching, so a bad ID fails here rather than returning an empty network. `rate_limited`: 429 response from CourtListener. `invalid_date`: filed_after is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. Both directions resolve the source cluster before searching, so a bad ID fails here rather than returning an empty network. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `invalid_date`: filed_after is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."

removedOutput schema / properties / next_cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changedcourtlistener_get_docket21 fields changed

removedOutput schema / properties / assigned_to / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / assigned_to / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / date_terminated / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / date_terminated / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / entries / items / properties / documents / items / properties / attachment_number / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / entries / items / properties / documents / items / properties / attachment_number / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / entries / items / properties / documents / items / properties / document_number / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / entries / items / properties / documents / items / properties / document_number / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / entries / items / properties / documents / items / properties / filepath_local / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / entries / items / properties / documents / items / properties / filepath_local / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / entries / items / properties / documents / items / properties / page_count / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / entries / items / properties / documents / items / properties / page_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / entries / items / properties / entry_number / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / entries / items / properties / entry_number / type
```
Added value: +[
+  "number",
+  "null"
+]
```

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler."

removedOutput schema / properties / next_cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / pacer_case_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / pacer_case_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / referred_to / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / referred_to / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changedcourtlistener_get_financial_disclosure7 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Disclosure ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Disclosure ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler."

removedOutput schema / properties / page_count / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / page_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / pdf_url / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / pdf_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / person_id / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / person_id / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changedcourtlistener_get_judge45 fields changed
- removedOutput schema / properties / dob / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / dob / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / dob_city / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / dob_city / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / dob_granularity / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / dob_granularity / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / dob_state / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / dob_state / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / dod / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / dod / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / dod_granularity / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / dod_granularity / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / education / items / properties / degree / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / education / items / properties / degree / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / education / items / properties / degree_label / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / education / items / properties / degree_label / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / education / items / properties / year / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / education / items / properties / year / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- changedOutput schema / properties / error / properties / data / properties / reason / description
```
Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Person ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Person ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler."
```
- removedOutput schema / properties / fjc_id / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / fjc_id / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / political_affiliations / items / properties / date_end / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / political_affiliations / items / properties / date_end / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / political_affiliations / items / properties / date_start / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / political_affiliations / items / properties / date_start / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / positions / items / properties / appointer / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / appointer / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / positions / items / properties / date_confirmation / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / date_confirmation / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / positions / items / properties / date_nominated / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / date_nominated / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / positions / items / properties / date_start / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / date_start / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / positions / items / properties / date_start_granularity / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / date_start_granularity / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / positions / items / properties / date_termination / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / date_termination / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / positions / items / properties / date_termination_granularity / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / date_termination_granularity / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / positions / items / properties / nomination_process / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / nomination_process / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / positions / items / properties / termination_reason / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / termination_reason / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / positions / items / properties / termination_reason_label / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / termination_reason_label / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changedcourtlistener_get_opinion5 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. `unknown_section`: A requested sections name matches no opinion variant in this cluster. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `unknown_section`: A requested sections name matches no opinion variant in this cluster. Other values are possible when a failure originates below the handler."

removedOutput schema / properties / opinions / items / properties / author_id / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / opinions / items / properties / author_id / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / opinions / items / properties / download_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / opinions / items / properties / download_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changedcourtlistener_get_oral_argument3 fields changed

removedOutput schema / properties / download_url / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / download_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Audio ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. `unknown_section`: A requested sections name is not a field of the oral argument record. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Audio ID does not exist in CourtListener. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `unknown_section`: A requested sections name is not a field of the oral argument record. Other values are possible when a failure originates below the handler."

Changedcourtlistener_get_parties11 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener or has no RECAP party data. `rate_limited`: 429 response from CourtListener. Each call to this tool makes at least two upstream requests. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener or has no RECAP party data. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Each call to this tool makes at least two upstream requests. Other values are possible when a failure originates below the handler."

removedOutput schema / properties / next_cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / parties / items / properties / attorneys / items / properties / date_action / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / parties / items / properties / attorneys / items / properties / date_action / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / parties / items / properties / attorneys / items / properties / role_code / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / parties / items / properties / attorneys / items / properties / role_code / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / parties / items / properties / role / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / parties / items / properties / role / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / total_parties / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / total_parties / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changedcourtlistener_lookup_citation21 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `not_found`: CourtListener could not parse any citation out of the submitted text. A citation that parses but matches nothing is a result with status 404, not this error. `rate_limited`: 429 response from CourtListener. `empty_citation`: citation is empty or whitespace-only after trimming — no request is sent. `citation_too_long`: citation exceeds the 64000-character ceiling CourtListener accepts — no request is sent. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `not_found`: CourtListener could not parse any citation out of the submitted text. A citation that parses but matches nothing is a result with status 404, not this error. `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_citation`: citation is empty or whitespace-only after trimming — no request is sent. `citation_too_long`: citation exceeds the 64000-character ceiling CourtListener accepts — no request is sent. Other values are possible when a failure originates below the handler."

removedOutput schema / properties / matches / items / properties / clusters / items / properties / case_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / matches / items / properties / clusters / items / properties / case_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / matches / items / properties / clusters / items / properties / cite_count / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / matches / items / properties / clusters / items / properties / cite_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / matches / items / properties / clusters / items / properties / cluster_id / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / matches / items / properties / clusters / items / properties / cluster_id / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / matches / items / properties / clusters / items / properties / court / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / matches / items / properties / clusters / items / properties / court / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / matches / items / properties / clusters / items / properties / court_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / matches / items / properties / clusters / items / properties / court_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / matches / items / properties / clusters / items / properties / date_filed / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / matches / items / properties / clusters / items / properties / date_filed / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / matches / items / properties / clusters / items / properties / docket_id / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / matches / items / properties / clusters / items / properties / docket_id / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / matches / items / properties / clusters / items / properties / judges / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / matches / items / properties / clusters / items / properties / judges / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / matches / items / properties / clusters / items / properties / precedential_status / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / matches / items / properties / clusters / items / properties / precedential_status / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / matches / items / properties / normalized_citation / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / matches / items / properties / normalized_citation / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changedcourtlistener_lookup_courts3 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler."

removedOutput schema / properties / next_cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changedcourtlistener_search_dockets19 fields changed
- changedOutput schema / properties / error / properties / data / properties / reason / description
```
Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."
```
- removedOutput schema / properties / next_cursor / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / assigned_to / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / assigned_to / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / date_terminated / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / date_terminated / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / pacer_case_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / pacer_case_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / referred_to / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / referred_to / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / sample_documents / items / properties / document_number / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / sample_documents / items / properties / document_number / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / sample_documents / items / properties / entry_number / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / sample_documents / items / properties / entry_number / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / sample_documents / items / properties / filepath_local / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / sample_documents / items / properties / filepath_local / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / sample_documents / items / properties / page_count / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / sample_documents / items / properties / page_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changedcourtlistener_search_financial_disclosures9 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. Other values are possible when a failure originates below the handler."

removedOutput schema / properties / next_cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / results / items / properties / page_count / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / page_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / results / items / properties / pdf_url / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / pdf_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / results / items / properties / person_id / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / person_id / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changedcourtlistener_search_judges10 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. Other values are possible when a failure originates below the handler."

removedOutput schema / properties / next_cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / results / items / properties / current_position / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "appointer": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Name of the appointing president (e.g. \"Obama, Barack Hussein, II\"); null if elected or not recorded."
-      },
-      "court": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Court full name; null for non-judicial positions."
-      },
-      "court_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Court identifier for use in filter parameters; null for non-judicial positions."
-      },
-      "date_start": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Date the position started; null if not recorded."
-      },
-      "date_termination": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Date the position ended; null while the judge still holds it."
-      },
-      "job_title": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Free-text title for non-judicial roles (e.g. \"Assistant district attorney\"); null for judicial positions."
-      },
-      "organization_name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Employer for non-judicial roles; null for judicial positions."
-      },
-      "position_type": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Judicial position title (e.g. \"Judge\", \"Chief Judge\"); null for non-judicial positions — see job_title."
-      },
-      "selection_method": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "How the judge reached the position (e.g. \"Appointment (President)\", \"Election (Partisan)\"); null if not recorded."
-      },
-      "termination_reason": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Why the position ended (e.g. \"Appointed to Other Judgeship\", \"Retirement\"); null while still serving."
-      }
-    },
-    "required": [
-      "court",
-      "court_id",
-      "position_type",
-      "job_title",
-      "organization_name",
-      "appointer",
-      "selection_method",
-      "date_start",
-      "date_termination",
-      "termination_reason"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "appointer": {
+        "description": "Name of the appointing president (e.g. \"Obama, Barack Hussein, II\"); null if elected or not recorded.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "court": {
+        "description": "Court full name; null for non-judicial positions.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "court_id": {
+        "description": "Court identifier for use in filter parameters; null for non-judicial positions.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "date_start": {
+        "description": "Date the position started; null if not recorded.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "date_termination": {
+        "description": "Date the position ended; null while the judge still holds it.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "job_title": {
+        "description": "Free-text title for non-judicial roles (e.g. \"Assistant district attorney\"); null for judicial positions.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "organization_name": {
+        "description": "Employer for non-judicial roles; null for judicial positions.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "position_type": {
+        "description": "Judicial position title (e.g. \"Judge\", \"Chief Judge\"); null for non-judicial positions — see job_title.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "selection_method": {
+        "description": "How the judge reached the position (e.g. \"Appointment (President)\", \"Election (Partisan)\"); null if not recorded.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "termination_reason": {
+        "description": "Why the position ended (e.g. \"Appointed to Other Judgeship\", \"Retirement\"); null while still serving.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "court",
+      "court_id",
+      "position_type",
+      "job_title",
+      "organization_name",
+      "appointer",
+      "selection_method",
+      "date_start",
+      "date_termination",
+      "termination_reason"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / results / items / properties / dob / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / dob / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / results / items / properties / dob_city / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / dob_city / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / results / items / properties / dob_state / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / dob_state / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changedcourtlistener_search_opinions10 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener — minute, hour, or day throttle hit. `invalid_query`: Query uses invalid field syntax or unsupported operators. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."

changedOutput schema / properties / error / properties / data / properties / reason / examples

Previous value: -[
-  "rate_limited",
-  "invalid_query",
-  "empty_query",
-  "invalid_date"
-]New value: +[
+  "rate_limited",
+  "empty_query",
+  "invalid_date"
+]

removedOutput schema / properties / next_cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / results / items / properties / opinions / items / properties / author_id / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / results / items / properties / opinions / items / properties / author_id / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / results / items / properties / opinions / items / properties / download_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / results / items / properties / opinions / items / properties / download_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / results / items / properties / opinions / items / properties / local_path / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / results / items / properties / opinions / items / properties / local_path / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changedcourtlistener_search_oral_arguments9 fields changed

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: argued_after or argued_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 from CourtListener, or no request slot opened within the wait budget. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: argued_after or argued_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler."

removedOutput schema / properties / next_cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / results / items / properties / date_argued / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / date_argued / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / results / items / properties / download_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / results / items / properties / download_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / results / items / properties / local_path / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / local_path / type
```
Added value: +[
+  "string",
+  "null"
+]
```

14 tool updatesAug 25, 2026

Changedcourtlistener_get_citations6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "source_cluster_id",
+      "source_case_name",
+      "direction",
+      "results",
+      "next_cursor",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. Both directions resolve the source cluster before searching, so a bad ID fails here rather than returning an empty network. `rate_limited`: 429 response from CourtListener. `invalid_date`: filed_after is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "rate_limited",
+            "invalid_date"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "source_cluster_id",
-  "source_case_name",
-  "direction",
-  "results",
-  "next_cursor",
-  "totalCount"
-]

Changedcourtlistener_get_docket6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "docket_id",
+      "case_name",
+      "case_name_full",
+      "court",
+      "court_id",
+      "date_filed",
+      "date_terminated",
+      "docket_number",
+      "pacer_case_id",
+      "assigned_to",
+      "referred_to",
+      "cause",
+      "jury_demand",
+      "jurisdiction_type",
+      "total_entries",
+      "entries_page",
+      "next_cursor",
+      "entries"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "rate_limited"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "docket_id",
-  "case_name",
-  "case_name_full",
-  "court",
-  "court_id",
-  "date_filed",
-  "date_terminated",
-  "docket_number",
-  "pacer_case_id",
-  "assigned_to",
-  "referred_to",
-  "cause",
-  "jury_demand",
-  "jurisdiction_type",
-  "total_entries",
-  "entries_page",
-  "next_cursor",
-  "entries"
-]

Changedcourtlistener_get_financial_disclosure6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "disclosure_id",
+      "person_id",
+      "year",
+      "report_type",
+      "page_count",
+      "has_been_extracted",
+      "is_amended",
+      "pdf_url",
+      "counts",
+      "kind"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Disclosure ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "rate_limited"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "disclosure_id",
-  "person_id",
-  "year",
-  "report_type",
-  "page_count",
-  "has_been_extracted",
-  "is_amended",
-  "pdf_url",
-  "counts",
-  "kind"
-]

Changedcourtlistener_get_judge6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "person_id",
+      "name",
+      "gender",
+      "dob",
+      "dob_granularity",
+      "dob_city",
+      "dob_state",
+      "dod",
+      "dod_granularity",
+      "fjc_id",
+      "aba_ratings",
+      "political_affiliations",
+      "education",
+      "positions",
+      "positionsShown",
+      "truncated"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Person ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "rate_limited"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "person_id",
-  "name",
-  "gender",
-  "dob",
-  "dob_granularity",
-  "dob_city",
-  "dob_state",
-  "dod",
-  "dod_granularity",
-  "fjc_id",
-  "aba_ratings",
-  "political_affiliations",
-  "education",
-  "positions",
-  "positionsShown",
-  "truncated"
-]

Changedcourtlistener_get_opinion6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "cluster_id",
+      "case_name",
+      "case_name_full",
+      "court",
+      "court_id",
+      "date_filed",
+      "docket_id",
+      "docket_number",
+      "judges",
+      "citations",
+      "cite_count",
+      "precedential_status",
+      "syllabus",
+      "posture",
+      "kind"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Cluster ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. `unknown_section`: A requested sections name matches no opinion variant in this cluster. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "rate_limited",
+            "unknown_section"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "cluster_id",
-  "case_name",
-  "case_name_full",
-  "court",
-  "court_id",
-  "date_filed",
-  "docket_id",
-  "docket_number",
-  "judges",
-  "citations",
-  "cite_count",
-  "precedential_status",
-  "syllabus",
-  "posture",
-  "kind"
-]

Changedcourtlistener_get_oral_argument6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "kind"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Audio ID does not exist in CourtListener. `rate_limited`: 429 response from CourtListener. `unknown_section`: A requested sections name is not a field of the oral argument record. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "rate_limited",
+            "unknown_section"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required
```
Removed value: -[
-  "kind"
-]
```

Changedcourtlistener_get_parties6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "docket_id",
+      "total_parties",
+      "next_cursor",
+      "parties"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: Docket ID does not exist in CourtListener or has no RECAP party data. `rate_limited`: 429 response from CourtListener. Each call to this tool makes at least two upstream requests. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "rate_limited"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "docket_id",
-  "total_parties",
-  "next_cursor",
-  "parties"
-]

Changedcourtlistener_lookup_citation6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "matches",
+      "queriedCitation"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `not_found`: CourtListener could not parse any citation out of the submitted text. A citation that parses but matches nothing is a result with status 404, not this error. `rate_limited`: 429 response from CourtListener. `empty_citation`: citation is empty or whitespace-only after trimming — no request is sent. `citation_too_long`: citation exceeds the 64000-character ceiling CourtListener accepts — no request is sent. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "not_found",
+            "rate_limited",
+            "empty_citation",
+            "citation_too_long"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "matches",
-  "queriedCitation"
-]

Changedcourtlistener_lookup_courts6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "page",
+      "next_cursor",
+      "courts",
+      "all_matching_court_ids",
+      "all_matching_court_ids_complete",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "rate_limited"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "page",
-  "next_cursor",
-  "courts",
-  "all_matching_court_ids",
-  "all_matching_court_ids_complete",
-  "totalCount"
-]

Changedcourtlistener_search_dockets6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "results",
+      "next_cursor",
+      "coverage_note",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "rate_limited",
+            "empty_query",
+            "invalid_date"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "results",
-  "next_cursor",
-  "coverage_note",
-  "totalCount"
-]

Changedcourtlistener_search_financial_disclosures6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "results",
+      "next_cursor"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "rate_limited"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "results",
-  "next_cursor"
-]

Changedcourtlistener_search_judges6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "results",
+      "next_cursor",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "rate_limited",
+            "empty_query"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "results",
-  "next_cursor",
-  "totalCount"
-]

Changedcourtlistener_search_opinions6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "results",
+      "next_cursor",
+      "totalCount",
+      "effectiveQuery"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener — minute, hour, or day throttle hit. `invalid_query`: Query uses invalid field syntax or unsupported operators. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: filed_after or filed_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "rate_limited",
+            "invalid_query",
+            "empty_query",
+            "invalid_date"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "results",
-  "next_cursor",
-  "totalCount",
-  "effectiveQuery"
-]

Changedcourtlistener_search_oral_arguments6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "results",
+      "next_cursor",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `rate_limited`: 429 response from CourtListener. `empty_query`: q is empty or whitespace-only after trimming — no request is sent. `invalid_date`: argued_after or argued_before is not a valid ISO 8601 calendar date. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "rate_limited",
+            "empty_query",
+            "invalid_date"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "results",
-  "next_cursor",
-  "totalCount"
-]

1 tool updateJul 30, 2026

Changedcourtlistener_lookup_courts2 fields changed

changedInput schema / properties / jurisdiction / description

Previous value: -"Jurisdiction type. F=Federal Appellate (circuit courts, SCOTUS), FD=Federal District, FB=Federal Bankruptcy, FBP=Federal Bankruptcy Panel, FS=Federal Special (USITC, FISC, etc.), C=Circuit (historical), I=International, T=Territory, ST=State Trial, SS=State Supreme, SAG=State Attorney General, SAL=State Legislature, SA=State Appellate, S=State (other), TT=Tribal/Territory. Omit to list all."New value: +"Jurisdiction type — CourtListener's own court classification, one code per court: F=Federal Appellate, FD=Federal District, FB=Federal Bankruptcy, FBP=Federal Bankruptcy Panel, FS=Federal Special, S=State Supreme, SA=State Appellate, ST=State Trial, SS=State Special, SAG=State Attorney General, TRS=Tribal Supreme, TRA=Tribal Appellate, TRT=Tribal Trial, TRX=Tribal Special, TS=Territory Supreme, TA=Territory Appellate, TT=Territory Trial, TSP=Territory Special, MA=Military Appellate, MT=Military Trial, C=Committee, I=International. Omit to list all. SCOTUS and the numbered circuits are F; USITC and FISC are FS. Upstream's Testing code is not offered here: /courts/ excludes testing courts from every response, so a filter on it can only ever return nothing. Accepted but matching no court as of the 2026-07-30 snapshot: TSP, MT. Courts whose stored jurisdiction is not one of these codes (njcirctsussex, ohctapp1) are unreachable through this filter at any value — the value they store is not one the filter accepts. Pass those ids straight to the tool that needs them, or list with no jurisdiction filter."

changedInput schema / properties / jurisdiction / enum

Previous value: -[
-  "F",
-  "FD",
-  "FB",
-  "FBP",
-  "FS",
-  "C",
-  "I",
-  "T",
-  "ST",
-  "SS",
-  "SAG",
-  "SAL",
-  "SA",
-  "S",
-  "TT"
-]New value: +[
+  "F",
+  "FD",
+  "FB",
+  "FBP",
+  "FS",
+  "S",
+  "SA",
+  "ST",
+  "SS",
+  "SAG",
+  "TRS",
+  "TRA",
+  "TRT",
+  "TRX",
+  "TS",
+  "TA",
+  "TT",
+  "TSP",
+  "MA",
+  "MT",
+  "C",
+  "I"
+]

3 tool updatesJul 30, 2026

Changedcourtlistener_get_judge5 fields changed

addedOutput schema / properties / notice

Added value: +{
+  "description": "Present only when positions[] was truncated: what was withheld.",
+  "type": "string"
+}

changedOutput schema / properties / positions / description

Previous value: -"Every position on record, across all courts — judicial appointments plus non-judicial roles (private practice, prosecutor, professor), which carry no court and describe themselves in job_title."New value: +"Positions on record, across all courts — judicial appointments plus non-judicial roles (private practice, prosecutor, professor), which carry no court and describe themselves in job_title. CourtListener paginates this list and the walk is bounded, so read the truncated flag before treating it as a complete career."

addedOutput schema / properties / positionsShown

Added value: +{
+  "description": "Number of position records returned.",
+  "type": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when the bounded /positions/ page walk stopped with pages outstanding — positions[] is then a prefix of the person's record, not the whole of it. False when the walk reached the end.",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "person_id",
-  "name",
-  "gender",
-  "dob",
-  "dob_granularity",
-  "dob_city",
-  "dob_state",
-  "dod",
-  "dod_granularity",
-  "fjc_id",
-  "aba_ratings",
-  "political_affiliations",
-  "education",
-  "positions"
-]New value: +[
+  "person_id",
+  "name",
+  "gender",
+  "dob",
+  "dob_granularity",
+  "dob_city",
+  "dob_state",
+  "dod",
+  "dod_granularity",
+  "fjc_id",
+  "aba_ratings",
+  "political_affiliations",
+  "education",
+  "positions",
+  "positionsShown",
+  "truncated"
+]

Changedcourtlistener_lookup_citation5 fields changed

addedInput schema / properties / max_court_lookups

Added value: +{
+  "default": 4,
+  "description": "How many distinct dockets this call may spend a request on to resolve cluster courts. The lookup itself is metered separately by CourtListener (per citation submitted), so this budget is drawn entirely from the ordinary per-request allowance — published free tier 5/min, 50/hour, 125/day, varying by token tier. 0 skips court resolution and costs nothing beyond the lookup; 20 is the ceiling. Clusters past the budget come back with court null and court_resolution \"over_budget\".",
+  "maximum": 20,
+  "minimum": 0,
+  "type": "integer"
+}

changedOutput schema / properties / matches / items / properties / clusters / items / properties / court / description

Previous value: -"Court display name. The citation-lookup payload carries no court, so this is resolved from the cluster's docket — one extra request each, capped at 4 distinct dockets per call. Null when that lookup was skipped past the cap, failed, or the cluster has no docket_id; the response notice reports how many clusters were left unresolved. Pass docket_id to courtlistener_get_docket, or cluster_id to courtlistener_get_opinion, to resolve one."New value: +"Court display name. The citation-lookup payload carries no court, so this is resolved from the cluster's docket — one extra request each, capped by max_court_lookups (default 4 distinct dockets per call). Null when that lookup was skipped past the budget, failed, or the cluster has no docket_id; court_resolution says which. Pass docket_id to courtlistener_get_docket, or cluster_id to courtlistener_get_opinion, to resolve one."

addedOutput schema / properties / matches / items / properties / clusters / items / properties / court_resolution

Added value: +{
+  "description": "Why court/court_id are or are not populated: \"resolved\" the docket lookup returned a court; \"no_docket\" the cluster carries no docket_id, so nothing can be resolved; \"lookup_failed\" a request was spent on the docket and it yielded no court; \"over_budget\" no request was spent because max_court_lookups ran out or the walk stopped on a rate limit — raise max_court_lookups or fetch that docket directly.",
+  "enum": [
+    "resolved",
+    "no_docket",
+    "lookup_failed",
+    "over_budget"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / matches / items / properties / clusters / items / required

Previous value: -[
-  "cluster_id",
-  "case_name",
-  "court",
-  "court_id",
-  "date_filed",
-  "docket_id",
-  "citations",
-  "cite_count",
-  "precedential_status",
-  "judges"
-]New value: +[
+  "cluster_id",
+  "case_name",
+  "court",
+  "court_id",
+  "court_resolution",
+  "date_filed",
+  "docket_id",
+  "citations",
+  "cite_count",
+  "precedential_status",
+  "judges"
+]

changedOutput schema / properties / notice / description

Previous value: -"Caveats on this result: a recovery hint when no citation in the input resolved to a case, and a count of clusters whose court the per-call docket cap left unresolved. Absent when neither applies."New value: +"Caveats on this result: a recovery hint when no citation in the input resolved to a case, and counts of the clusters whose court went unresolved — split by whether the per-call docket budget ran out or an attempted lookup returned nothing, since only the first is worth retrying with a larger budget. Absent when none applies."

Changedcourtlistener_lookup_courts4 fields changed

addedOutput schema / properties / all_matching_court_ids

Added value: +{
+  "description": "Every court id matching the same filters, from a snapshot of /courts/ bundled with this server (taken 2026-07-30) — the complete set, not just this page, and free of any request. Paging `courts` is only needed for the fields a court id alone does not carry (full_name, citation_string, scraper flags). Empty when more than 1000 courts match, since a prefix of the set would be indistinguishable from the whole of it — check all_matching_court_ids_complete before reading emptiness as \"no courts match\". A court added or retired upstream since the snapshot date appears in `courts` but may be missing here.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / all_matching_court_ids_complete

Added value: +{
+  "description": "True when all_matching_court_ids holds every matching court id. False when more than 1000 courts match: the list is withheld whole rather than truncated, and the notice gives the count and how to narrow.",
+  "type": "boolean"
+}

changedOutput schema / properties / courts / description

Previous value: -"Matching courts."New value: +"Matching courts on this page."

changedOutput schema / required

Previous value: -[
-  "page",
-  "next_cursor",
-  "courts",
-  "totalCount"
-]New value: +[
+  "page",
+  "next_cursor",
+  "courts",
+  "all_matching_court_ids",
+  "all_matching_court_ids_complete",
+  "totalCount"
+]

4 tool updatesJul 30, 2026

Changedcourtlistener_get_oral_argument6 fields changed

changedInput schema / properties / sections / description

Previous value: -"Section identifiers to retrieve in full, from a prior outline response (e.g. [\"transcript\"]). Omit for the full record, or an outline if it overflows the inline budget."New value: +"Section identifiers to retrieve, from a prior outline response — [\"transcript\"] is the only one that adds anything, since every other field is returned regardless. A selection that omits \"transcript\" therefore returns the record without it. Omit this argument entirely for the whole record, or the record minus an oversized transcript."

changedOutput schema / properties / kind / description

Previous value: -"'full' returns the record (or the selected sections); 'outline' lists retrievable sections when the transcript overflows the inline byte budget."New value: +"'full' carries the transcript inline; 'outline' withholds it and lists it as a retrievable section because it overflows the inline byte budget. Every other field of the record is present either way."

changedOutput schema / properties / retrieval_notice / description

Previous value: -"How to re-call the tool for specific sections when the record overflows."New value: +"How to re-call the tool for the transcript when it overflows the inline budget."

changedOutput schema / properties / sections / description

Previous value: -"Retrievable sections, largest first — pass names to `sections` on a re-call."New value: +"Sections withheld from this response — only ever `transcript`; pass its name to `sections` on a re-call. Absent when nothing was withheld."

changedOutput schema / properties / sections / items / description

Previous value: -"A retrievable section of the record and its serialized byte size."New value: +"A withheld section of the record and its serialized byte size."

changedOutput schema / properties / transcript / description

Previous value: -"Speech-to-text transcript; empty string if transcription has not completed."New value: +"Speech-to-text transcript; empty string if transcription has not completed. The only field an outline response withholds — re-call with sections:[\"transcript\"] to retrieve it."

Changedcourtlistener_get_parties7 fields changed

addedInput schema / properties / cursor

Added value: +{
+  "description": "Pagination cursor from a previous response's next_cursor field. Omit for the first page. This is an opaque token, not a page number — CourtListener cursor-paginates this endpoint, so a numeric value selects nothing and re-serves the first page.",
+  "type": "string"
+}

removedInput schema / properties / page

Removed value: -{
-  "default": 1,
-  "description": "Page number (1-indexed). Use with page_size to paginate large party lists.",
-  "maximum": 9007199254740991,
-  "minimum": 1,
-  "type": "integer"
-}

changedOutput schema / properties / next_cursor / description

Previous value: -"Next page number to pass as the `page` argument (this list is page-paginated); null when this is the last page."New value: +"Opaque pagination cursor for the next page — pass it back as the `cursor` argument; null when this is the last page."

removedOutput schema / properties / page

Removed value: -{
-  "description": "Current page number.",
-  "type": "number"
-}

changedOutput schema / properties / totalCount / description

Previous value: -"Total parties on this docket across all pages — present only when the API reports a numeric count (this endpoint returns it as a URL by default, so it is absent for any list spanning more than one page)."New value: +"Total parties on this docket across all pages — this endpoint reports its count as a URL rather than a number, so the total is only derivable when the first page is also the last, and is absent for any list spanning more than one page."

changedOutput schema / properties / total_parties / description

Previous value: -"Total parties on this docket across all pages; null when upstream reports no count (a multi-page list whose total is unknown until the last page)."New value: +"Total parties on this docket across all pages; null when no total is derivable — CourtListener serves the count as a URL rather than a number here, so it is only known when the first page is also the last."

changedOutput schema / required

Previous value: -[
-  "docket_id",
-  "total_parties",
-  "page",
-  "next_cursor",
-  "parties"
-]New value: +[
+  "docket_id",
+  "total_parties",
+  "next_cursor",
+  "parties"
+]

Changedcourtlistener_lookup_citation10 fields changed

changedInput schema / properties / citation / description

Previous value: -"Legal citation string to resolve (e.g., \"410 U.S. 113\", \"347 U.S. 483\", \"93 S. Ct. 705\"). Supports standard reporter formats."New value: +"Text to extract citations from — normally a single citation (e.g., \"410 U.S. 113\", \"347 U.S. 483\", \"93 S. Ct. 705\"), but any passage works and every citation in it is resolved. Supports standard reporter formats. Up to 64000 characters, which is CourtListener's own ceiling; a longer passage is rejected here rather than spending a request to be refused upstream."

removedOutput schema / properties / case_name

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Case name; null if not found."
-}

removedOutput schema / properties / citations

Removed value: -{
-  "description": "All known citation strings for this case.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / cluster_id

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Opinion cluster ID — null if the citation is not in the CourtListener database."
-}

removedOutput schema / properties / court

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Court display name; null if not found."
-}

removedOutput schema / properties / date_filed

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Date the opinion was filed; null if not found."
-}

addedOutput schema / properties / matches

Added value: +{
+  "description": "One entry per citation CourtListener extracted from the input, in the order they appear.",
+  "items": {
+    "additionalProperties": false,
+    "description": "One citation found in the submitted text and everything it resolved to.",
+    "properties": {
+      "citation": {
+        "description": "The citation as CourtListener matched it in the submitted text.",
+        "type": "string"
+      },
+      "clusters": {
+        "description": "Cases this citation resolved to — empty when status is not 200 or 300, and more than one when status is 300.",
+        "items": {
+          "additionalProperties": false,
+          "description": "An opinion cluster this citation resolved to.",
+          "properties": {
+            "case_name": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Case name; null if not recorded."
+            },
+            "citations": {
+              "description": "All known citation strings for this case.",
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "cite_count": {
+              "anyOf": [
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Times other opinions cite this case — a rough authority weight. Null if not recorded."
+            },
+            "cluster_id": {
+              "anyOf": [
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Opinion cluster ID — pass to courtlistener_get_opinion. Null when upstream sent no ID."
+            },
+            "court": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Court display name. The citation-lookup payload carries no court, so this is resolved from the cluster's docket — one extra request each, capped at 4 distinct dockets per call. Null when that lookup was skipped past the cap, failed, or the cluster has no docket_id; the response notice reports how many clusters were left unresolved. Pass docket_id to courtlistener_get_docket, or cluster_id to courtlistener_get_opinion, to resolve one."
+            },
+            "court_id": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Court identifier for the `court` filter on the search tools (e.g. \"scotus\"); null under the same conditions as `court`."
+            },
+            "date_filed": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Date the opinion was filed; null if not recorded."
+            },
+            "docket_id": {
+              "anyOf": [
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Linked docket — pass to courtlistener_get_docket. Null if not recorded."
+            },
+            "judges": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Free-text judge names; null or empty if not recorded."
+            },
+            "precedential_status": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Publication status (e.g. \"Published\", \"Unpublished\"); null if not recorded."
+            }
+          },
+          "required": [
+            "cluster_id",
+            "case_name",
+            "court",
+            "court_id",
+            "date_filed",
+            "docket_id",
+            "citations",
+            "cite_count",
+            "precedential_status",
+            "judges"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "error_message": {
+        "description": "CourtListener's explanation when status is not 200; empty string otherwise.",
+        "type": "string"
+      },
+      "normalized_citation": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Canonical citation form used by CourtListener; null if not resolved."
+      },
+      "status": {
+        "description": "Resolution status for this citation alone: 200 one case, 300 several candidates, 400 unrecognized reporter, 404 no case found, 429 past the per-request citation cap. Not the status of the request, which succeeded.",
+        "type": "number"
+      },
+      "status_label": {
+        "description": "status decoded to a label.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "citation",
+      "normalized_citation",
+      "status",
+      "status_label",
+      "error_message",
+      "clusters"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / normalized_citation

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Canonical citation form used by CourtListener; null if not resolved."
-}

changedOutput schema / properties / notice / description

Previous value: -"Recovery hint when the citation is not in the database — suggests alternative lookup strategies."New value: +"Caveats on this result: a recovery hint when no citation in the input resolved to a case, and a count of clusters whose court the per-call docket cap left unresolved. Absent when neither applies."

changedOutput schema / required

Previous value: -[
-  "cluster_id",
-  "case_name",
-  "court",
-  "date_filed",
-  "citations",
-  "normalized_citation",
-  "queriedCitation"
-]New value: +[
+  "matches",
+  "queriedCitation"
+]

Changedcourtlistener_lookup_courts4 fields changed

removedInput schema / properties / in_use

Removed value: -{
-  "default": true,
-  "description": "When true (default), only return courts currently scraped by CourtListener. Set to false to include historical or inactive courts.",
-  "type": "boolean"
-}

changedInput schema / properties / page / description

Previous value: -"Page number (1-indexed). CourtListener caps /courts/ at ~20 rows per page regardless of size, so the full list (~472 courts) spans ~24 pages — pass the next_cursor from a previous response here to page through them."New value: +"Page number (1-indexed). CourtListener serves /courts/ at a fixed 20 rows per page and ignores any requested page size, so the number of pages is the enrichment totalCount divided by 20 — there is no way to pull a larger page. Pass the next_cursor from a previous response here to walk them one call at a time."

addedInput schema / properties / status

Added value: +{
+  "default": "active",
+  "description": "Which bench to return. 'active' (default) returns only courts CourtListener currently scrapes; 'inactive' returns only the historical and defunct courts it no longer scrapes; 'any' returns both. The two filtered sets are disjoint, so 'any' is the only value that reaches the whole list — but reaching all of it means paging, one call per 20 courts, and the inactive bench is several times larger than the active one. Prefer the narrowest value that answers the question, and narrow with jurisdiction rather than paging the full list.",
+  "enum": [
+    "active",
+    "inactive",
+    "any"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / next_cursor / description

Previous value: -"Next page number to pass as the `page` argument (this list is page-paginated at ~20 rows/page); null when this is the last page."New value: +"Next page number to pass as the `page` argument (this list is page-paginated at a fixed 20 rows/page); null when this is the last page — a non-null value means the courts shown are a partial view of the filtered set."

2 tool updatesJul 30, 2026

Changedcourtlistener_get_judge21 fields changed

changedOutput schema / properties / dob / description

Previous value: -"Date of birth; null if not recorded."New value: +"Date of birth as CourtListener stores it, always full ISO 8601 — but the month and day are placeholders unless dob_granularity is \"day\". Read dob_granularity before presenting this as an exact date. Null if not recorded."

addedOutput schema / properties / dob_granularity

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Precision actually recorded for dob: \"year\", \"month\", or \"day\". Null when CourtListener recorded no precision. An unrecognized upstream value passes through unchanged."
+}

changedOutput schema / properties / dod / description

Previous value: -"Date of death; null if living or not recorded."New value: +"Date of death as CourtListener stores it, always full ISO 8601 — precision qualified by dod_granularity, as with dob. Null if living or not recorded."

addedOutput schema / properties / dod_granularity

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Precision actually recorded for dod: \"year\", \"month\", or \"day\". Null when CourtListener recorded no precision."
+}

changedOutput schema / properties / education / items / properties / degree / description

Previous value: -"Degree level; null if not recorded."New value: +"Raw CourtListener degree-level code (e.g. \"ba\"); null if not recorded."

addedOutput schema / properties / education / items / properties / degree_label

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Degree level expanded to a readable label (e.g. \"Juris Doctor (J.D.)\"). An unmapped code passes through as the code itself; null if not recorded."
+}

changedOutput schema / properties / education / items / required

Previous value: -[
-  "school",
-  "degree",
-  "year"
-]New value: +[
+  "school",
+  "degree",
+  "degree_label",
+  "year"
+]

changedOutput schema / properties / positions / description

Previous value: -"All judicial positions held, across all courts."New value: +"Every position on record, across all courts — judicial appointments plus non-judicial roles (private practice, prosecutor, professor), which carry no court and describe themselves in job_title."

changedOutput schema / properties / positions / items / description

Previous value: -"Judicial position record."New value: +"Position record — judicial or otherwise."

changedOutput schema / properties / positions / items / properties / date_start / description

Previous value: -"Date position started; null if not recorded."New value: +"Date the position started as CourtListener stores it, always full ISO 8601 — the month and day are placeholders unless date_start_granularity is \"day\". Null if not recorded."

addedOutput schema / properties / positions / items / properties / date_start_granularity

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Precision actually recorded for date_start: \"year\", \"month\", or \"day\". Null when CourtListener recorded no precision."
+}

changedOutput schema / properties / positions / items / properties / date_termination / description

Previous value: -"Date position ended; null if current."New value: +"Date the position ended as CourtListener stores it, always full ISO 8601 — precision qualified by date_termination_granularity. Null if current."

addedOutput schema / properties / positions / items / properties / date_termination_granularity

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Precision actually recorded for date_termination: \"year\", \"month\", or \"day\". Null when CourtListener recorded no precision."
+}

addedOutput schema / properties / positions / items / properties / job_title

Added value: +{
+  "description": "Free-text title for a role with no position_type code (e.g. \"Assistant district attorney\"); empty on judicial rows.",
+  "type": "string"
+}

addedOutput schema / properties / positions / items / properties / organization_name

Added value: +{
+  "description": "Employer for a non-judicial role; empty on judicial rows, which use court.",
+  "type": "string"
+}

changedOutput schema / properties / positions / items / properties / position_type / description

Previous value: -"Position title (e.g., \"District Judge\", \"Circuit Judge\", \"Justice\")."New value: +"Raw CourtListener position-type code (e.g. \"jud\", \"c-jud\") — the value the /positions/ position_type filter takes. Empty for non-judicial roles, which describe themselves in job_title."

addedOutput schema / properties / positions / items / properties / position_type_label

Added value: +{
+  "description": "Position type expanded to a readable label (e.g. \"Judge\", \"Chief Judge\"). An unmapped code passes through as the code itself; empty for non-judicial roles.",
+  "type": "string"
+}

changedOutput schema / properties / positions / items / properties / termination_reason / description

Previous value: -"Reason for termination; null if still serving."New value: +"Raw CourtListener termination-reason code (e.g. \"other_pos\"); null if still serving."

addedOutput schema / properties / positions / items / properties / termination_reason_label

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Termination reason expanded to a readable label (e.g. \"Appointed to Other Judgeship\"). An unmapped code passes through as the code itself; null if still serving."
+}

changedOutput schema / properties / positions / items / required

Previous value: -[
-  "court",
-  "court_id",
-  "position_type",
-  "appointer",
-  "nomination_process",
-  "date_nominated",
-  "date_confirmation",
-  "date_start",
-  "date_termination",
-  "termination_reason"
-]New value: +[
+  "court",
+  "court_id",
+  "position_type",
+  "position_type_label",
+  "job_title",
+  "organization_name",
+  "appointer",
+  "nomination_process",
+  "date_nominated",
+  "date_confirmation",
+  "date_start",
+  "date_start_granularity",
+  "date_termination",
+  "date_termination_granularity",
+  "termination_reason",
+  "termination_reason_label"
+]

changedOutput schema / required

Previous value: -[
-  "person_id",
-  "name",
-  "gender",
-  "dob",
-  "dob_city",
-  "dob_state",
-  "dod",
-  "fjc_id",
-  "aba_ratings",
-  "political_affiliations",
-  "education",
-  "positions"
-]New value: +[
+  "person_id",
+  "name",
+  "gender",
+  "dob",
+  "dob_granularity",
+  "dob_city",
+  "dob_state",
+  "dod",
+  "dod_granularity",
+  "fjc_id",
+  "aba_ratings",
+  "political_affiliations",
+  "education",
+  "positions"
+]

Changedcourtlistener_get_opinion3 fields changed

changedOutput schema / properties / opinions / items / properties / type / description

Previous value: -"Opinion type: \"lead-opinion\", \"concurrence\", \"dissent\", \"combined-opinion\", etc."New value: +"Raw CourtListener opinion-type code (e.g. \"030concurrence\"); the numeric prefix is a sort key, not part of the type. Empty when upstream recorded none."

addedOutput schema / properties / opinions / items / properties / type_label

Added value: +{
+  "description": "Opinion type expanded to the label courtlistener_search_opinions serves for the same variant: \"lead-opinion\", \"concurrence-opinion\", \"dissent\", \"combined-opinion\", etc. An unmapped code passes through as the code itself.",
+  "type": "string"
+}

changedOutput schema / properties / opinions / items / required

Previous value: -[
-  "id",
-  "type",
-  "author_id",
-  "per_curiam",
-  "html_text",
-  "plain_text",
-  "cites",
-  "download_url"
-]New value: +[
+  "id",
+  "type",
+  "type_label",
+  "author_id",
+  "per_curiam",
+  "html_text",
+  "plain_text",
+  "cites",
+  "download_url"
+]

1 tool updateJul 30, 2026

Changedcourtlistener_get_citations3 fields changed

changedInput schema / properties / page_size / description

Previous value: -"Number of results to request (default 20). For direction=\"cited_by\", CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results. direction=\"citing\" returns at most page_size (the cited-opinion list is sliced before querying) — fewer when the opinion cites fewer than page_size distinct opinions. Each citation tool call costs one request against the rate limit — keep low for multi-hop traversal."New value: +"Number of results to request (default 20). For direction=\"cited_by\", CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results. direction=\"citing\" returns at most page_size (the cited-opinion list is sliced before querying) — fewer when the opinion cites fewer than page_size distinct opinions. Either direction costs three requests against the rate limit (a case with many opinion variants costs one more per extra variant page) — keep low for multi-hop traversal."

changedOutput schema / properties / notice / description

Previous value: -"Recovery hint when no citations are found — echoes direction and filters, suggests alternatives."New value: +"Context when no citations are returned — either that this page had no match under the filters and more pages remain, or a recovery hint echoing direction and filters."

changedOutput schema / properties / totalCount / description

Previous value: -"Total citations in the requested direction."New value: +"Total citations in the requested direction. For \"cited_by\" it counts matching clusters with the court and filed_after filters applied. For \"citing\" it counts the distinct opinions this case cites, before any filter — so it exceeds what the filters make reachable, and runs higher than the result rows, which are clusters (several cited opinions in one case collapse to one row)."

1 tool updateJul 30, 2026

Changedcourtlistener_get_parties9 fields changed

changedInput schema / properties / page_size / description

Previous value: -"Number of parties per page (1–10). Each call makes two upstream requests (parties + attorney batch) — keep low to stay within the free-tier rate limit."New value: +"Requested number of parties per page (1–10). CourtListener paginates this endpoint at a fixed size and does not honor the requested value, so a page can come back larger than asked for."

addedOutput schema / properties / parties / items / properties / attorneys / items / properties / date_action

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Date the attorney–party relationship ended; null while the attorney is still of record."
+}

addedOutput schema / properties / parties / items / properties / attorneys / items / properties / role

Added value: +{
+  "description": "role_code decoded to a label (e.g., \"Lead attorney\"). Codes 5–9 (\"Self-terminated\" through \"Disbarred\") mean the attorney is no longer of record. The stringified code when upstream sends a value outside the documented enum, \"Unrecorded\" when it sends none.",
+  "type": "string"
+}

addedOutput schema / properties / parties / items / properties / attorneys / items / properties / role_code / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```

changedOutput schema / properties / parties / items / properties / attorneys / items / properties / role_code / description

Previous value: -"Numeric attorney role code from the party–attorney relationship (e.g., 1 = Lead attorney)."New value: +"Numeric attorney role code from the party–attorney relationship (1 = Attorney to be noticed, 2 = Lead attorney, 3 = Attorney in sealed group, 4 = Pro hac vice, 5 = Self-terminated, 6 = Terminated, 7 = Suspended, 8 = Inactive, 9 = Disbarred, 10 = Unknown); null when upstream recorded no code."

removedOutput schema / properties / parties / items / properties / attorneys / items / properties / role_code / type
```
Removed value: -"number"
```

changedOutput schema / properties / parties / items / properties / attorneys / items / required

Previous value: -[
-  "attorney_id",
-  "name",
-  "contact_raw",
-  "role_code"
-]New value: +[
+  "attorney_id",
+  "name",
+  "contact_raw",
+  "role_code",
+  "role",
+  "date_action"
+]

changedOutput schema / properties / totalCount / description

Previous value: -"Total parties on this docket across all pages."New value: +"Total parties on this docket across all pages — present only when the API reports a numeric count (this endpoint returns it as a URL by default, so it is absent for any list spanning more than one page)."

changedOutput schema / required

Previous value: -[
-  "docket_id",
-  "total_parties",
-  "page",
-  "next_cursor",
-  "parties",
-  "totalCount"
-]New value: +[
+  "docket_id",
+  "total_parties",
+  "page",
+  "next_cursor",
+  "parties"
+]

5 tool updatesJul 30, 2026

Changedcourtlistener_get_citations1 field changed

changedOutput schema / properties / results / items / properties / snippet / description

Previous value: -"Text excerpt showing context around the citation (where available)."New value: +"Matched text excerpt from the related opinion, taken from the first opinion variant in the cluster that carries one; empty string when none does. It is a relevance preview for the cluster, not necessarily text surrounding the citation itself."

Changedcourtlistener_search_dockets15 fields changed

addedOutput schema / properties / results / items / properties / attorneys

Added value: +{
+  "description": "Attorney names of record on this docket; empty when none are recorded.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / case_name_full

Added value: +{
+  "description": "Full case name with all parties; empty string when not recorded.",
+  "type": "string"
+}

removedOutput schema / properties / results / items / properties / document_count

Removed value: -{
-  "description": "Number of documents available in RECAP.",
-  "type": "number"
-}

addedOutput schema / properties / results / items / properties / firms

Added value: +{
+  "description": "Law firm names of record on this docket; empty when none are recorded.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / jurisdiction_type

Added value: +{
+  "description": "Basis of federal jurisdiction (e.g. \"Federal Question\"); empty string when not recorded.",
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / referred_to

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Referred magistrate judge name; null if not recorded."
+}

changedOutput schema / properties / results / items / properties / sample_documents / description

Previous value: -"Up to 3 sample filings from this docket."New value: +"Up to 3 sample filings matched on this docket — a search excerpt, not the docket's full filing list. Call courtlistener_get_docket for every entry."

changed

Output schema / properties / results / items / properties / sample_documents / items / properties / date_filed / description

Previous value: -"Date the document was filed."New value: +"Date the parent docket entry was filed; empty string when not recorded."

addedOutput schema / properties / results / items / properties / sample_documents / items / properties / document_type

Added value: +{
+  "description": "Document classification (e.g. \"PACER Document\", \"RECAP Document\"); empty string when not recorded.",
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / sample_documents / items / properties / entry_number

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Docket entry number this document belongs to; null if unnumbered."
+}

addedOutput schema / properties / results / items / properties / sample_documents / items / properties / filepath_local

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Fully-qualified RECAP storage URL (https://storage.courtlistener.com/...) for the document; null when no copy is stored."
+}

addedOutput schema / properties / results / items / properties / sample_documents / items / properties / page_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Page count; null if not recorded."
+}

changedOutput schema / properties / results / items / properties / sample_documents / items / required

Previous value: -[
-  "id",
-  "description",
-  "date_filed",
-  "document_number",
-  "is_available"
-]New value: +[
+  "id",
+  "description",
+  "date_filed",
+  "document_number",
+  "entry_number",
+  "document_type",
+  "page_count",
+  "filepath_local",
+  "is_available"
+]

addedOutput schema / properties / results / items / properties / suit_nature

Added value: +{
+  "description": "Nature-of-suit label, usually prefixed with its PACER code (e.g. \"830 Patent\"); empty string when not recorded.",
+  "type": "string"
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "docket_id",
-  "case_name",
-  "court",
-  "court_id",
-  "date_filed",
-  "date_terminated",
-  "docket_number",
-  "pacer_case_id",
-  "assigned_to",
-  "cause",
-  "jury_demand",
-  "parties",
-  "document_count",
-  "sample_documents"
-]New value: +[
+  "docket_id",
+  "case_name",
+  "case_name_full",
+  "court",
+  "court_id",
+  "date_filed",
+  "date_terminated",
+  "docket_number",
+  "pacer_case_id",
+  "assigned_to",
+  "referred_to",
+  "cause",
+  "jury_demand",
+  "suit_nature",
+  "jurisdiction_type",
+  "parties",
+  "attorneys",
+  "firms",
+  "sample_documents"
+]

Changedcourtlistener_search_judges4 fields changed

changedOutput schema / properties / results / items / properties / aba_rating / description

Previous value: -"ABA qualification ratings."New value: +"ABA qualification labels (e.g. \"Well Qualified\", \"Qualified\"), one per rating on record — not the rating codes."

changedOutput schema / properties / results / items / properties / current_position / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "appointer": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Appointing president; null if elected or not recorded."
-      },
-      "court": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Court where currently serving; null if not applicable."
-      },
-      "court_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Court identifier."
-      },
-      "date_start": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Date position started."
-      },
-      "position_type": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Position title (e.g., \"District Judge\")."
-      }
-    },
-    "required": [
-      "court",
-      "court_id",
-      "position_type",
-      "appointer",
-      "date_start"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "appointer": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Name of the appointing president (e.g. \"Obama, Barack Hussein, II\"); null if elected or not recorded."
+      },
+      "court": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Court full name; null for non-judicial positions."
+      },
+      "court_id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Court identifier for use in filter parameters; null for non-judicial positions."
+      },
+      "date_start": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Date the position started; null if not recorded."
+      },
+      "date_termination": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Date the position ended; null while the judge still holds it."
+      },
+      "job_title": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Free-text title for non-judicial roles (e.g. \"Assistant district attorney\"); null for judicial positions."
+      },
+      "organization_name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Employer for non-judicial roles; null for judicial positions."
+      },
+      "position_type": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Judicial position title (e.g. \"Judge\", \"Chief Judge\"); null for non-judicial positions — see job_title."
+      },
+      "selection_method": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "How the judge reached the position (e.g. \"Appointment (President)\", \"Election (Partisan)\"); null if not recorded."
+      },
+      "termination_reason": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Why the position ended (e.g. \"Appointed to Other Judgeship\", \"Retirement\"); null while still serving."
+      }
+    },
+    "required": [
+      "court",
+      "court_id",
+      "position_type",
+      "job_title",
+      "organization_name",
+      "appointer",
+      "selection_method",
+      "date_start",
+      "date_termination",
+      "termination_reason"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / results / items / properties / current_position / description

Previous value: -"Current or most recent position; null if not available."New value: +"The position with no termination date, or — when several or none qualify — the one with the latest start date. Null when the record carries no positions. courtlistener_get_judge returns the full appointment history."

changedOutput schema / properties / results / items / properties / political_affiliation / description

Previous value: -"Political affiliation codes."New value: +"Party labels (e.g. \"Democratic\", \"Republican\"), one per recorded affiliation — not the single-letter codes the political_affiliation input filter takes."

Changedcourtlistener_search_opinions3 fields changed

addedOutput schema / properties / results / items / properties / opinions

Added value: +{
+  "description": "Opinion variants filed in this case (majority, concurrence, dissent, per curiam). Empty when upstream returned none.",
+  "items": {
+    "additionalProperties": false,
+    "description": "One opinion variant within the cluster.",
+    "properties": {
+      "author_id": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Person ID of the authoring judge — pass to courtlistener_get_judge; null when unattributed."
+      },
+      "cites": {
+        "description": "Opinion IDs this variant cites. These are opinion-level IDs, not cluster IDs — courtlistener_get_opinion and courtlistener_get_citations both take a cluster_id, so do not pass these values to them directly.",
+        "items": {
+          "type": "number"
+        },
+        "type": "array"
+      },
+      "download_url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "URL of the originating court's copy; null when none was recorded. Often plain HTTP and prone to rot — prefer local_path."
+      },
+      "id": {
+        "description": "Opinion ID for this variant — identifies one opinion within the cluster (the cluster itself is cluster_id).",
+        "type": "number"
+      },
+      "local_path": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "CourtListener-hosted copy of the source document (https://storage.courtlistener.com/...); null if not stored."
+      },
+      "per_curiam": {
+        "description": "True when the opinion was issued per curiam (by the court).",
+        "type": "boolean"
+      },
+      "type": {
+        "description": "Variant type as an expanded label (e.g. \"combined-opinion\", \"lead-opinion\", \"dissent\").",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "author_id",
+      "per_curiam",
+      "download_url",
+      "local_path",
+      "cites"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / results / items / properties / snippet / description

Previous value: -"Matched text excerpt from the opinion."New value: +"Matched text excerpt, taken from the first entry in opinions[] that carries one; empty string when no variant has an excerpt. CourtListener does not mark which variant the search matched, so treat this as a relevance preview for the cluster, not as an excerpt attributable to a specific opinion — read opinions[] to attribute it."

changedOutput schema / properties / results / items / required

Previous value: -[
-  "cluster_id",
-  "case_name",
-  "case_name_full",
-  "court",
-  "court_id",
-  "date_filed",
-  "docket_number",
-  "docket_id",
-  "citations",
-  "cite_count",
-  "judges",
-  "status",
-  "snippet"
-]New value: +[
+  "cluster_id",
+  "case_name",
+  "case_name_full",
+  "court",
+  "court_id",
+  "date_filed",
+  "docket_number",
+  "docket_id",
+  "citations",
+  "cite_count",
+  "judges",
+  "status",
+  "snippet",
+  "opinions"
+]

Changedcourtlistener_search_oral_arguments2 fields changed

changedOutput schema / properties / results / items / properties / download_url / description

Previous value: -"Direct MP3 download URL; null if not available."New value: +"MP3 URL at the originating court; null if not recorded. Often plain HTTP and prone to rot as courts reorganize — prefer local_path, CourtListener's durable copy."

changedOutput schema / properties / results / items / properties / local_path / description

Previous value: -"Local storage path on CourtListener servers; null if not available."New value: +"CourtListener-hosted copy of the recording (https://storage.courtlistener.com/...); null if not stored."

2 tool updatesJul 16, 2026

Changedcourtlistener_lookup_courts4 fields changed

addedInput schema / properties / page

Added value: +{
+  "default": 1,
+  "description": "Page number (1-indexed). CourtListener caps /courts/ at ~20 rows per page regardless of size, so the full list (~472 courts) spans ~24 pages — pass the next_cursor from a previous response here to page through them.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / next_cursor

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Next page number to pass as the `page` argument (this list is page-paginated at ~20 rows/page); null when this is the last page."
+}

addedOutput schema / properties / page

Added value: +{
+  "description": "Current page number (1-indexed).",
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "courts",
-  "totalCount"
-]New value: +[
+  "page",
+  "next_cursor",
+  "courts",
+  "totalCount"
+]

Changedcourtlistener_search_financial_disclosures1 field changed

changedInput schema / properties / year / description

Previous value: -"Filing year to filter by (e.g., 2022). Filters the fetched filings — pair with judge_id for complete per-judge results. Omit to return all available years."New value: +"Filing year to filter by (e.g., 2022). Applied client-side to the fetched page only — CourtListener rejects a server-side year param, so filings for this year on later pages are not included. When a page has no match for the year but more pages remain, next_cursor is returned; pass it as cursor to check the next page. Omit to return all years on the page."

5 tool updatesJul 16, 2026
- Changedcourtlistener_lookup_citation1 field changed
  - removedInput schema / properties / citation / minLength
```
Removed value: -1
```
- Changedcourtlistener_search_dockets1 field changed
  - removedInput schema / properties / q / minLength
```
Removed value: -1
```
- Changedcourtlistener_search_judges1 field changed
  - removedInput schema / properties / q / minLength
```
Removed value: -1
```
- Changedcourtlistener_search_opinions1 field changed
  - removedInput schema / properties / q / minLength
```
Removed value: -1
```
- Changedcourtlistener_search_oral_arguments1 field changed
  - removedInput schema / properties / q / minLength
```
Removed value: -1
```
1 tool updateJul 11, 2026
- Addedcourtlistener_get_financial_disclosure

3 tool updatesJul 10, 2026

Changedcourtlistener_get_citations2 fields changed

changedInput schema / properties / page_size / default
```
Previous value: -10New value: +20
```

changedInput schema / properties / page_size / description

Previous value: -"Number of results (1–20). Each citation tool call costs one request against the rate limit — keep page_size low for multi-hop traversal."New value: +"Number of results to request (default 20). For direction=\"cited_by\", CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 results. direction=\"citing\" returns at most page_size (the cited-opinion list is sliced before querying) — fewer when the opinion cites fewer than page_size distinct opinions. Each citation tool call costs one request against the rate limit — keep low for multi-hop traversal."

Changedcourtlistener_get_docket6 fields changed

addedInput schema / properties / entries_page

Added value: +{
+  "default": 1,
+  "description": "Page of docket entries to fetch (1-indexed). Docket entries are page-paginated at 20 per page; pass the next_cursor from a previous response here to page through large cases.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / entries_page_size / description

Previous value: -"Number of docket entries to return (1–50). Large cases can have hundreds of entries."New value: +"Requested docket entries per page. NOTE: CourtListener ignores this value — /docket-entries/ always returns a fixed 20-entry page regardless of what is passed. Use entries_page to reach entries beyond the first 20 (large cases can have hundreds)."

changedOutput schema / properties / entries / description

Previous value: -"Docket entries up to entries_page_size."New value: +"Docket entries for this page (fixed at 20 per page; entries_page_size is not honored by upstream)."

addedOutput schema / properties / entries_page

Added value: +{
+  "description": "Current entries page number (1-indexed).",
+  "type": "number"
+}

addedOutput schema / properties / next_cursor

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Next page number to pass as the `entries_page` argument (docket entries are page-paginated); null when this is the last page."
+}

changedOutput schema / required

Previous value: -[
-  "docket_id",
-  "case_name",
-  "case_name_full",
-  "court",
-  "court_id",
-  "date_filed",
-  "date_terminated",
-  "docket_number",
-  "pacer_case_id",
-  "assigned_to",
-  "referred_to",
-  "cause",
-  "jury_demand",
-  "jurisdiction_type",
-  "total_entries",
-  "entries"
-]New value: +[
+  "docket_id",
+  "case_name",
+  "case_name_full",
+  "court",
+  "court_id",
+  "date_filed",
+  "date_terminated",
+  "docket_number",
+  "pacer_case_id",
+  "assigned_to",
+  "referred_to",
+  "cause",
+  "jury_demand",
+  "jurisdiction_type",
+  "total_entries",
+  "entries_page",
+  "next_cursor",
+  "entries"
+]

Changedcourtlistener_search_financial_disclosures1 field changed

changedInput schema / properties / page_size / description

Previous value: -"Number of filings to return (1–20)."New value: +"Number of filings to request (default 20). CourtListener enforces a minimum of 20 results per page regardless of the value passed — you will always receive at least 20 filings."

2 tool updatesJul 10, 2026

Changedcourtlistener_get_opinion6 fields changed

addedInput schema / properties / sections

Added value: +{
+  "description": "Opinion variant identifiers to retrieve in full, from a prior outline response (e.g. [\"opinion_12345\"]). Omit to return all variants, or an outline if they overflow the inline byte budget.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / kind

Added value: +{
+  "description": "'full' returns the opinion variants (all, or a selected subset); 'outline' lists each variant as a retrievable section (opinion_<id>) when the opinions overflow the inline byte budget. Cluster metadata is present either way.",
+  "enum": [
+    "full",
+    "outline"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / opinions / description

Previous value: -"All opinion variants within this cluster."New value: +"All opinion variants within this cluster. Present in full mode; omitted in outline mode — re-call with sections:[\"opinion_<id>\"] to retrieve specific variants."

addedOutput schema / properties / retrieval_notice

Added value: +{
+  "description": "How to re-call the tool for specific opinion variants when the opinions overflow.",
+  "type": "string"
+}

addedOutput schema / properties / sections

Added value: +{
+  "description": "Retrievable opinion variants, largest first — pass names to `sections` on a re-call.",
+  "items": {
+    "additionalProperties": false,
+    "description": "A retrievable opinion variant (opinion_<id>) and its serialized byte size.",
+    "properties": {
+      "bytes": {
+        "description": "Serialized byte size of the section",
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "name": {
+        "description": "Section identifier — pass in `sections` to retrieve it",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "bytes"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "cluster_id",
-  "case_name",
-  "case_name_full",
-  "court",
-  "court_id",
-  "date_filed",
-  "docket_id",
-  "docket_number",
-  "judges",
-  "citations",
-  "cite_count",
-  "precedential_status",
-  "syllabus",
-  "posture",
-  "opinions"
-]New value: +[
+  "cluster_id",
+  "case_name",
+  "case_name_full",
+  "court",
+  "court_id",
+  "date_filed",
+  "docket_id",
+  "docket_number",
+  "judges",
+  "citations",
+  "cite_count",
+  "precedential_status",
+  "syllabus",
+  "posture",
+  "kind"
+]

Changedcourtlistener_get_oral_argument5 fields changed

addedInput schema / properties / sections

Added value: +{
+  "description": "Section identifiers to retrieve in full, from a prior outline response (e.g. [\"transcript\"]). Omit for the full record, or an outline if it overflows the inline budget.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / kind

Added value: +{
+  "description": "'full' returns the record (or the selected sections); 'outline' lists retrievable sections when the transcript overflows the inline byte budget.",
+  "enum": [
+    "full",
+    "outline"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / retrieval_notice

Added value: +{
+  "description": "How to re-call the tool for specific sections when the record overflows.",
+  "type": "string"
+}

addedOutput schema / properties / sections

Added value: +{
+  "description": "Retrievable sections, largest first — pass names to `sections` on a re-call.",
+  "items": {
+    "additionalProperties": false,
+    "description": "A retrievable section of the record and its serialized byte size.",
+    "properties": {
+      "bytes": {
+        "description": "Serialized byte size of the section",
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "name": {
+        "description": "Section identifier — pass in `sections` to retrieve it",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "bytes"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "oral_argument_id",
-  "case_name",
-  "case_name_full",
-  "docket_id",
-  "duration_seconds",
-  "download_url",
-  "judges",
-  "panel_ids",
-  "has_transcript",
-  "transcript"
-]New value: +[
+  "kind"
+]

2 tool updatesJun 30, 2026

Changedcourtlistener_get_judge2 fields changed

changedOutput schema / properties / positions / items / properties / appointer / description

Previous value: -"Appointing president name; null if elected or not recorded."New value: +"Position URI of the appointing authority (e.g., \".../positions/123/\"), not resolved to a name; null if elected or not recorded."

changedOutput schema / properties / positions / items / properties / nomination_process / description

Previous value: -"Nomination process; null if not recorded."New value: +"Selection method, expanded to a readable label (e.g., \"Appointment (President)\"); null if not recorded."

Changedcourtlistener_get_opinion1 field changed

changedOutput schema / properties / opinions / items / properties / html_text / description

Previous value: -"Full opinion text as HTML; may be empty if only a download URL is available."New value: +"Full opinion text as HTML, drawn from the best available variant (citation-linked when present); empty only when no HTML text is stored — use download_url then."

2 tool updatesJun 30, 2026

Changedcourtlistener_get_docket3 fields changed

changedOutput schema / properties / entries / items / properties / documents / items / properties / document_number / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changed

Output schema / properties / entries / items / properties / documents / items / properties / document_number / description

Previous value: -"PACER document number; null if not assigned."New value: +"PACER document number as a string (e.g. \"1\"); attachments can be non-integer like \"70-1\". Null if not assigned."

changed

Output schema / properties / entries / items / properties / documents / items / properties / filepath_local / description

Previous value: -"RECAP storage URL for available documents; null if not available."New value: +"Fully-qualified RECAP storage URL (https://storage.courtlistener.com/...) for the document; null if not available."

Changedcourtlistener_get_parties4 fields changed

changedOutput schema / properties / next_cursor / description

Previous value: -"Opaque cursor for the next page; null when this is the last page."New value: +"Next page number to pass as the `page` argument (this list is page-paginated); null when this is the last page."

addedOutput schema / properties / total_parties / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / total_parties / description

Previous value: -"Total number of parties on this docket across all pages."New value: +"Total parties on this docket across all pages; null when upstream reports no count (a multi-page list whose total is unknown until the last page)."

removedOutput schema / properties / total_parties / type
```
Removed value: -"number"
```

Related MCP Connectors

Court Records MCPOAuth
net.nexlab
Search US federal and state court records through CourtListener and the RECAP archive
Government Data Legal & Compliance Open Data
1
CourtListener B
io.github.Vaquill-AI
MCP for CourtListener: US federal and state opinions, dockets, judges, plus eCFR regulations.
Legal & Compliance Government Data
3424
Docket Nexus A
com.docketnexus
Search public U.S. federal litigation: companies, cases, dockets and document metadata.
Government Data Legal & Compliance
61
ezelOAuth
ai.ezel
Search U.S. case law, fetch opinions, and ask matter-aware legal questions over your documents.
Legal & Compliance Search
2

Related MCP Servers

CourtListener MCP Server
Legal & Compliance Government Data
Travis-Prall
F
license
Not graded
quality
A
maintenance
Enables LLM-friendly access to the CourtListener legal database and eCFR for searching legal opinions, court cases, judges, documents, and federal regulations.
Updated 2 days ago (2026-10-01 19:07 UTC)
12
-
CourtListener Legal Research
Legal & Compliance Government Data Research & Data
khizar-anjum
A
license
Not graded
quality
D
maintenance
Enables legal research across 3,352 U.S. courts using the CourtListener API, providing access to case search, precedent analysis, judge patterns, citation validation, and federal PACER dockets through natural language queries.
Updated a year ago (2025-09-08 18:22 UTC)
45 npm
3
MIT
court-listener
Legal & Compliance Government Data Open Data
pipeworx-io
A
license
Not graded
quality
B
maintenance
Enables AI agents to query and access legal data from the Free Law Project's CourtListener API, including court opinions, judges, and dockets, with basic access requiring no authentication.
Updated 8 days ago (2026-09-25 23:01 UTC)
161 npm
MIT
mcp-docket-alarm
Legal & Compliance Government Data
pipeworx-io
A
license
Not graded
quality
B
maintenance
Enables users to search and retrieve court docket records across US state, county, and federal courts, including PACER party searches, and to get full case details.
Updated 8 days ago (2026-09-25 23:36 UTC)
358 npm
MIT

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.

Server Details

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources