Skip to main content
Glama
jmaciasc-google

Google Threat Intelligence MCP Server

search_threats

Search for cybersecurity threats including threat actors, malware families, campaigns, reports, and vulnerabilities. Filter by type for precise, targeted results.

Instructions

Search threats in the Google Threat Intelligence platform.

Threats are modeled as collections. Once you get collections from this tool, you can use get_collection_report to fetch the full reports and their relationships.

IMPORTANT CONTEXT CLUE: Pay close attention to the user's request. If their request mentions specific kinds of threats such as "threat actor", "malware family", "campaign", "report", or "vulnerability", treat this as a strong signal that you must use the collection_type filter in your query to ensure relevant results. Using this filter significantly improves search precision.

Filtering by Type: To filter your search results to a specific type of threat, include the collection_type modifier within your query string. Syntax: collection_type:"<type>" Available <type> values:

  • "threat-actor": Use when the user asks about specific actors, groups, or APTs.

  • "malware-family": Use when the user asks about malware, trojans, viruses, ransomware families.

  • "software-toolkit": Use when the user asks about legit tools usually related to malware.

  • "campaign": Use when the user asks about specific attack campaigns.

  • "report": Use when the user is looking for analysis reports.

  • "vulnerability": Use when the user asks about specific CVEs or vulnerabilities.

  • "collection": A generic type, use only if no other type fits or if the user explicitly asks for generic "collections".

You can use order_by to sort the results by: "relevance", "creation_date". You can use the sign "+" to make it order ascending, or "-" to make it descending. By default is "relevance-"

When asked for latest threats, prioritize campaigns or vulnerabilities over reports.

Args: query (required): Search query to find threats. collection_type: Filter your search results to a specific type of threat limit: Limit the number of threats to retrieve. 5 by default. order_by: Order results by the given order key. "relevance-" by default.

Returns: List of collections, aka threats. They are full collection objects, you do not need to retrieve themusing the get_collection_reporttool. You may need to extend with relationships usingget_entities_related_to_a_collection` tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
order_byNorelevance-
collection_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description adequately discloses behavior: it returns a list of collection objects, and mentions the need for further tools to extend relationships. It explains ordering syntax and default limits. However, it does not cover error conditions, rate limits, or pagination behavior, but for a read-only search tool, transparency is sufficient.

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 structured with sections like 'IMPORTANT CONTEXT CLUE' and 'Filtering by Type', making it readable. It front-loads the main purpose. Some redundancy exists (e.g., repeating filter info in the Args section), but the length is justified by the detailed guidance it provides. Slight verbosity prevents a 5.

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

Completeness3/5

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

Given the four parameters and presence of an output schema, the description covers most essential aspects: return type, relationship to other tools, parameter syntax. However, it lacks guidance on error handling, result pagination, and critically, when to use this tool vs. the many specialized search siblings. This incomplete contextual mapping leaves the agent underinformed.

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?

The input schema has 0% description coverage, so the description must clarify parameters. It does so effectively: explains 'collection_type' with syntax and available values, 'order_by' with ordering keys and signs, 'query' as required search, and 'limit' as count with default. However, it does not specify query format or maximum limits, but overall compensates well for the missing schema descriptions.

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 clearly states it searches threats modeled as collections. It distinguishes from 'get_collection_report' by noting that tool fetches full reports. However, it does not differentiate from specialized sibling tools like 'search_threat_actors' or 'search_malware_families', which could cause confusion about which tool to use for specific threat types.

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 description gives explicit guidance on when to use the 'collection_type' filter based on user request, and offers ordering preferences for latest threats. However, it fails to provide guidance on when to use this broad search tool versus the specialized search tools (e.g., 'search_campaigns', 'search_vulnerabilities'), leaving a gap in decision-making for the agent.

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/jmaciasc-google/gti-mcp-server'

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