Looker MCP Server

search_content

Search across all Looker content including dashboards, looks, and explores. Retrieve matching items with titles, descriptions, and IDs.

Instructions

Search across all Looker content — dashboards, looks, explores, and more. Returns matching items with titles, descriptions, and IDs.

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_string": "<query_string>"
    },
    "name": "search_content"
  }
}

Input Schema

Name	Required	Description
`query_string`	Yes	Search query (full-text search)
`types`	No	Content types to search: 'dashboard', 'look', 'folder', etc.
`limit`	No	Maximum results to return

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.20.0May 29, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so description must compensate. It describes the matching behavior and returned fields, but lacks details on pagination, ordering, authentication, or depth of search. Output schema exists but is not visible in the definition.

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?

Two sentences, no filler. First sentence states the action, second states the result. Efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and the tool is a straightforward search with 3 parameters, the description covers the essential purpose and return structure adequately.

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% with all parameters already described. The description does not add new semantic meaning beyond the schema's descriptions for 'query_string', 'types', and 'limit'.

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?

Description clearly states the action 'Search across all Looker content' and lists examples (dashboards, looks, explores) and what it returns (titles, descriptions, IDs), distinguishing it from listing or running tools.

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?

Implicitly tells when to use (when searching across content types) but does not explicitly compare to sibling listing tools like list_dashboards or list_looks, leaving some interpretation to the agent.

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