Skip to main content
Glama
googleSandy

Google Threat Intelligence MCP Server

by googleSandy

search_campaigns

Search for threat campaigns using queries, returning collections of related threats that can be analyzed with detailed reports.

Instructions

Search threat campaigns in the Google Threat Intelligence platform.

Campaigns 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.

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-"

Args: query (required): Search query to find threats. limit: Limit the number of threats to retrieve. 10 by default. order_by: Order results by the given order key. "relevance-" by default.

Returns: List of collections, aka threats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo
order_byNorelevance-
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'search_campaigns' tool handler function. It delegates to _search_threats_by_collection_type with collection_type='campaign'.
    async def search_campaigns(
        query: str, ctx: Context, limit: int = 10, order_by: str = "relevance-", api_key: str = None
    ) -> typing.List[typing.Dict[str, typing.Any]]:
      """Search threat campaigns in the Google Threat Intelligence platform.
    
      Campaigns 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.
    
      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-"
    
      Args:
        query (required): Search query to find threats.
        limit: Limit the number of threats to retrieve. 10 by default.
        order_by: Order results by the given order key. "relevance-" by default.
    
      Returns:
        List of collections, aka threats.
      """
      res = await _search_threats_by_collection_type(
          query, "campaign", ctx, limit, order_by, api_key=api_key)
      return res
  • The underlying helper function _search_threats_by_collection_type used by search_campaigns. It queries the VirusTotal /collections API with a filter for the specific collection type (campaign).
    async def _search_threats_by_collection_type(
        query: str,
        collection_type: str,
        ctx: Context,
        limit: int = 10,
        order_by: str = "relevance-",
        api_key: str = None,
    ) -> typing.List[typing.Dict[str, typing.Any]]:
      """Search a given threat type in the Google Threat Intelligence platform,
    
      Args:
        query (required): Search query to find threats. If you want any threat, just pass an empty string.
        collection_type (required): Collection type. One of: "threat-actor", "malware-family", "campaign", "report", "vulnerability", "collection".
        limit: Limit the number of threats to retrieve. 10 by default.
        order_by: Order results by the given order key. "relevance-" by default.
    
      Returns:
        List of collections, aka threats.
      """
      if collection_type not in COLLECTION_TYPES:
          raise ValueError(
              f"wrong collection_type. Available collection_type are: {','.join(COLLECTION_TYPES)} ")
    
      async with vt_client(ctx, api_key=api_key) as client:
        res = await utils.consume_vt_iterator(
            client,
            "/collections",
            params={
                "filter": f"collection_type:{collection_type} {query}",
                "order": order_by,
                "relationships": COLLECTION_KEY_RELATIONSHIPS,
                "exclude_attributes": COLLECTION_EXCLUDED_ATTRS,
            },
            limit=limit,
        )
      return utils.sanitize_response([o.to_dict() for o in res])
  • The @server.tool() decorators that register 'search_campaigns' as an MCP tool with the FastMCP server.
    @server.tool()
    @server.tool()
  • The consume_vt_iterator utility that interfaces with the VT API to paginate through collection results.
    async def consume_vt_iterator(
        vt_client: vt.Client, endpoint: str, params: dict | None = None, limit: int = 10):
      """Consumes a vt.Iterator iterator and return the list of objects."""
      res = []
      async for obj in vt_client.iterator(endpoint, params=params, limit=limit):
        res.append(obj)
      return res
    
    
    async def fetch_object(
        vt_client: vt.Client,
        resource_collection_type: str,
        resource_type: str,
        resource_id: str,
        attributes: list[str] | None = None,
        relationships: list[str] | None = None,
        params: dict[str, typing.Any] | None = None):
      """Fetches objects from Google Threat Intelligence API."""
      logging.info(
          f"Fetching comprehensive {resource_collection_type} "
          f"report for id: {resource_id}")
      
      params = {k: v for k, v in params.items()} if params else {}
    
      # Retrieve a selection of object attributes and/or relationships.
      if attributes:
        params["attributes"] = ",".join(attributes)
      if relationships:
        params["relationships"] = ",".join(relationships)
    
      try:
        obj = await vt_client.get_object_async(
            f"/{resource_collection_type}/{resource_id}", params=params)
    
        if obj.error:
          logging.error(
              f"Error fetching main {resource_type} report for {resource_id}: {obj.error}"
          )
          return {
              "error": f"Failed to get main {resource_type} report: {obj.error}",
              # "details": report.get("details"),
          }
      except vt.error.APIError as e:
        logging.warning(
            f"VirusTotal API Error fetching {resource_type} {resource_id}: {e.code} - {e.message}"
        )
        return {
            "error": f"VirusTotal API Error: {e.code} - {e.message}",
            "details": f"The requested {resource_type} '{resource_id}' could not be found or there was an issue with the API request."
        }
      except Exception as e:
        logging.exception(
            f"Unexpected error fetching {resource_type} {resource_id}: {e}"
        )
        return {"error": "An unexpected internal error occurred."}
Behavior3/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It explains that the tool returns a list of collections (threats) and describes parameters, but does not address whether the tool is read-only, any auth requirements, rate limits, or potential side effects. The behavioral transparency is adequate but not comprehensive.

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?

The description is moderately concise but includes a docstring with sections like Args and Returns. It is longer than necessary but well-organized. Some redundancy could be trimmed, e.g., repeating default values already in schema.

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 existence of an output schema, the description adequately summarizes returns as a list of collections. It mentions the workflow with get_collection_report. However, it does not cover the 'api_key' parameter, nor does it fully differentiate from sibling search tools. Completeness is acceptable but has clear gaps.

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 description adds significant meaning beyond the schema (which had 0% parameter descriptions). It explains the 'query', 'limit', and 'order_by' parameters with details on sort options and defaults. However, it omits the 'api_key' parameter present in the schema, leaving a gap. Overall, it compensates well for the schema's lack of 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 threat campaigns on the Google Threat Intelligence platform. It distinguishes from siblings like search_threats by specifying 'campaigns' and mentions they are modeled as collections, but could be more explicit about what differentiates this from similar search tools.

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 provides some usage guidance by noting that after getting collections, one can use get_collection_report. However, it does not explicitly state when to avoid this tool in favor of alternatives like search_threats or other search tools, nor does it mention prerequisites or context.

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/googleSandy/gti-mcp-standalone'

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