Skip to main content
Glama

Search Google Patents

search_patents
Read-onlyIdempotent

Searches Google Patents by keywords, with optional inventor, assignee, country, status and date filters, and returns the source JSON (organic_results with title, patent_id, link and other fields). Use it for inventions and patent publications. It does not return full patent texts or claims, and is not for research papers (use search_scholar). A search with no matches is charged; errors are not. Required: query.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_patents"
  }
}

Input Schema

NameRequiredDescriptionDefault
numNoResults per page, integer 1-100, e.g. 20; omitted uses source default. No option surcharge; 5 credits per successful request.
pageNoOne-based result page, integer at least 1, e.g. 2; omitted uses source default. No option surcharge; 5 credits per successful request.
sortNoSort order: new (newest first) or old (oldest first), e.g. "new"; omitted uses source default. No option surcharge; 5 credits per successful request.
afterNoEarliest publication date included, YYYY-MM-DD, e.g. "2020-01-01"; omitted means no cutoff. No option surcharge; 5 credits per successful request.
queryYesRequired patent search keywords, e.g. "solar cell"; no default. No option surcharge; 5 credits per successful request.
beforeNoLatest publication date included, YYYY-MM-DD, e.g. "2025-12-31"; must not precede after; omitted means no cutoff. No option surcharge; 5 credits per successful request.
statusNoPatent status filter as used in Google Patents search URLs, e.g. "GRANT" or "APPLICATION"; omitted uses source default. No option surcharge; 5 credits per successful request.
countryNoPatent office country code, e.g. "US", "EP" or "JP"; omitted means any country. No option surcharge; 5 credits per successful request.
assigneeNoAssignee (owner) name filter, e.g. "Toyota"; omitted means any assignee. No option surcharge; 5 credits per successful request.
inventorNoInventor name filter, e.g. "Jane Smith"; omitted means any inventor. No option surcharge; 5 credits per successful request.
languageNoPatent language filter as used in Google Patents search URLs, e.g. "ENGLISH"; omitted uses source default. No option surcharge; 5 credits per successful request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / after / description
      Previous value: -"Publication start date in YYYY-MM-DD format; omitted means no cutoff. No option surcharge; 5 credits per successful request."New value: +"Earliest publication date included, YYYY-MM-DD, e.g. \"2020-01-01\"; omitted means no cutoff. No option surcharge; 5 credits per successful request."
    • changedInput schema / properties / assignee / description
      Previous value: -"Assignee name filter; omitted means any assignee. No option surcharge; 5 credits per successful request."New value: +"Assignee (owner) name filter, e.g. \"Toyota\"; omitted means any assignee. No option surcharge; 5 credits per successful request."
    • changedInput schema / properties / before / description
      Previous value: -"Publication cutoff date in YYYY-MM-DD format; omitted means no cutoff. No option surcharge; 5 credits per successful request."New value: +"Latest publication date included, YYYY-MM-DD, e.g. \"2025-12-31\"; must not precede after; omitted means no cutoff. No option surcharge; 5 credits per successful request."
    • changedInput schema / properties / country / description
      Previous value: -"Patent country code; omitted means any country. No option surcharge; 5 credits per successful request."New value: +"Patent office country code, e.g. \"US\", \"EP\" or \"JP\"; omitted means any country. No option surcharge; 5 credits per successful request."
    • changedInput schema / properties / inventor / description
      Previous value: -"Inventor name filter; omitted means any inventor. No option surcharge; 5 credits per successful request."New value: +"Inventor name filter, e.g. \"Jane Smith\"; omitted means any inventor. No option surcharge; 5 credits per successful request."
    • changedInput schema / properties / language / description
      Previous value: -"Result language code; omitted uses source default. No option surcharge; 5 credits per successful request."New value: +"Patent language filter as used in Google Patents search URLs, e.g. \"ENGLISH\"; omitted uses source default. No option surcharge; 5 credits per successful request."
    • changedInput schema / properties / num / description
      Previous value: -"Result count, integer 1-100; omitted uses source default. No option surcharge; 5 credits per successful request."New value: +"Results per page, integer 1-100, e.g. 20; omitted uses source default. No option surcharge; 5 credits per successful request."
    • changedInput schema / properties / page / description
      Previous value: -"Result page, integer at least 1; omitted uses source default. No option surcharge; 5 credits per successful request."New value: +"One-based result page, integer at least 1, e.g. 2; omitted uses source default. No option surcharge; 5 credits per successful request."
    • changedInput schema / properties / query / description
      Previous value: -"Required patent search keywords; no default. No option surcharge; 5 credits per successful request."New value: +"Required patent search keywords, e.g. \"solar cell\"; no default. No option surcharge; 5 credits per successful request."
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order: new or old; omitted uses source default. No option surcharge; 5 credits per successful request."New value: +"Sort order: new (newest first) or old (oldest first), e.g. \"new\"; omitted uses source default. No option surcharge; 5 credits per successful request."
    • changedInput schema / properties / status / description
      Previous value: -"Patent status filter; omitted uses source default. No option surcharge; 5 credits per successful request."New value: +"Patent status filter as used in Google Patents search URLs, e.g. \"GRANT\" or \"APPLICATION\"; omitted uses source default. No option surcharge; 5 credits per successful request."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: failed match searches are still billed, errors are not, and the payload is the raw source JSON rather than parsed patent documents. It stops short of describing pagination limits or result-count behavior, which for an 11-param, 100-result-per-page tool would have been useful.

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 compact sentences that front-load purpose, then output shape, then exclusions and the required parameter. No redundancy and nothing that fails to earn its place.

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 11-parameter search tool with no output schema, the description covers what the tool does, what it returns (composite field names), what it does not return (full texts, claims), the alternative for adjacent intent, and the billing caveat. An agent has everything needed to call it correctly.

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% — every parameter including the sort enum has its own description with format examples and cost notes — so the baseline of 3 applies. The description's list of filter dimensions (inventor, assignee, country, status, date) merely summarizes what the schema already documents in more detail.

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 Google Patents) plus the filter axes it supports and the shape of what comes back (source JSON with organic_results, title, patent_id, link). It also explicitly contrasts itself with search_scholar, so an agent can distinguish it from siblings 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 Guidelines5/5

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

Gives positive scope ('use it for inventions and patent publications') and explicit exclusions with a named alternative ('not for research papers (use search_scholar)'). It further bounds expectations by saying full patent texts and claims are not returned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources