Skip to main content
Glama

pinecone_delete_vectors

Delete vectors from a Pinecone index using vector IDs, metadata filters, or delete all vectors in a namespace.

Instructions

Delete vectors from a Pinecone index by ID or filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesPinecone API key
index_hostYesIndex host URL from describe_index
idsNoArray of vector IDs to delete
delete_allNoDelete all vectors in the namespace
namespaceNoNamespace to delete from
filterNoMetadata filter - delete matching vectors
Behavior2/5

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

No annotations are provided, and the description only mentions 'delete' without detailing permanence, reversibility, or side effects. The powerful 'delete_all' flag and use of namespace are not explained.

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?

One concise sentence with no wasted words. However, it could be restructured to include more context without increasing length significantly.

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

Completeness2/5

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

With 6 parameters and no output schema, the description is too minimal. It fails to explain parameter interactions (e.g., ids vs filter vs delete_all) or the impact of namespace. A more complete description is needed for a destructive operation.

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. The description adds no additional meaning beyond what the schema already provides for parameters.

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 clearly states the action (delete), the resource (vectors), and the two methods (by ID or filter). It is specific and distinguishes from siblings like upsert and query.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No context about prerequisites, when-not-to-use, or comparisons with other Pinecone 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/malamutemayhem/unclick'

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