Skip to main content
Glama
w0h1v

VirusTotal MCP Server

get_collection

Retrieve a VirusTotal collection by its ID to access threat actors, malware families, campaigns, or curated IOC sets. Optionally include relationships to fetch related IOCs like files, URLs, and domains.

Instructions

Retrieve a VirusTotal collection by ID. Collections represent threat actors, malware families, campaigns, intel reports, and curated IOC sets — often referenced from the related_threat_actors and collections relationships on other tools. Optionally include relationships (files, urls, domains, ip_addresses, references, threat_actors, related_collections, related_references, comments, owner, autogenerated_graphs) to fetch member IOCs in the same call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCollection ID (e.g. a threat-actor, malware family, campaign, or report identifier returned from a relationship lookup)
relationshipsNoOptional list of relationships to include in the response
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly indicates a read-only operation ('Retrieve') and explains the optional relationship inclusion. It does not mention destructive actions, authentication needs, or rate limits, but the behavior is transparent enough for a simple retrieval.

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?

The description is two sentences, with the primary action front-loaded. Every sentence adds value: the first defines the core function, the second clarifies the optional relationships feature. No unnecessary words.

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?

While the description explains the tool's purpose and relationship expansion, it does not describe the response format or structure. Given no output schema, this leaves a gap in understanding what the agent can expect to receive.

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 coverage is 100%, providing a baseline of 3. The description adds meaning by explaining that the 'id' parameter is a collection identifier from relationship lookups and lists the relationship options with context, going beyond the enum.

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?

The description states 'Retrieve a VirusTotal collection by ID' with a specific verb and resource. It further explains that collections represent threat actors, malware families, etc., distinguishing it from sibling tools that retrieve individual entities like files or domains.

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?

The description mentions optionally including relationships to fetch member IOCs, giving context on when to expand results. However, it does not explicitly state when not to use this tool or compare to alternatives beyond the implicit differentiation from sibling tools.

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/w0h1v/mcp-virustotal'

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