Skip to main content
Glama

google_dorks

Generate ready-to-click Google, Bing, and DuckDuckGo dork URLs for a domain or brand to find exposed files, login panels, subdomains, API keys, documents, and other public traces.

Instructions

Generate ready-to-click Google/Bing/DDG dork URLs for a domain or brand.

Categories: exposed_files, login_panels, directory_listing, git_exposure, subdomains, api_keys, documents, emails, parameters, cloud_storage, errors, all. Google blocks automated queries - open these URLs in a browser.

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": {
      "target": "<target>"
    },
    "name": "google_dorks"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
categoryNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the single most important behavioral trait: the tool returns clickable URLs, not scraped results, because search engines block automated queries. It omits secondary behavior such as how many URLs are emitted per category or how the target string is embedded, but the main trap for an agent is covered.

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 purpose sentence is front-loaded and the operational warning follows immediately; nothing is padded. The multi-line category list occupies most of the text, but it earns its place given the missing enum, though it could be tightened into a single line.

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 two-parameter URL-builder with no output schema and no annotations, the definition covers what the tool emits, all valid category values, the required target, and the key operational constraint. Only the volume/shape of the returned URL list is left unspecified, which is minor here.

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 description coverage is 0% and the 'category' parameter has no enum, so the schema alone leaves valid values undocumented. The description compensates by enumerating all twelve accepted categories (exposed_files, login_panels, ... all) and clarifying that 'target' is a domain or brand, which is meaningful value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Generate ready-to-click Google/Bing/DDG dork URLs for a domain or brand', and names the three engines covered. It is clear this produces URLs rather than search results, but it does not name a concrete alternative (e.g., browser_search) it differs from.

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

Usage Guidelines3/5

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

The line 'Google blocks automated queries - open these URLs in a browser' implies the correct usage mode (hand off to a human/browser, do not fetch) and rules out one misuse. However, it never states when to pick this over a sibling like browser_search or deep_osint, so the choice is left to inference.

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