Skip to main content
Glama
DerrickAppOrg

Derrick App

Official

Find First-Page Google Organic Results

derrick_serp_first_page
Read-only

Retrieve the first-page Google organic results for any query. Returns up to 10 results, useful for multi-source research and competitive analysis.

Instructions

Find First-Page Google Organic Results Enter text made of the column you want to search Cost: 3 credit(s) per call. Category: find::google

Returns the 10 organic Google results from the first page. More expensive than serp_first_result — use only when multiple sources are needed.

Args: queryValue: Select values you want to search

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryValueYesSelect values you want to search
Behavior4/5

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

Adds cost and exact number of results beyond annotations (readOnlyHint, openWorldHint). No contradictions.

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

Conciseness3/5

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

Some redundancy (title repeated), awkward phrasing ('Enter text made of the column'), could be more streamlined without losing information.

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?

Covers purpose, usage context, cost, and return count. Missing details like error handling or validation, but tool is simple and annotations cover read-only nature.

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 baseline is 3. Description adds no significant new parameter meaning beyond 'Select values you want to search'.

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?

Explicitly states it returns the 10 organic Google results from the first page, and distinguishes from sibling tool serp_first_result which returns only one result.

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?

Explicitly says 'More expensive than serp_first_result — use only when multiple sources are needed', providing clear when-to-use and when-not-to-use guidance with sibling comparison.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DerrickAppOrg/derrick-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server