Skip to main content
Glama
pinecone-io

Pinecone Developer MCP

Official
by pinecone-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Upsert Records

upsert-records
DestructiveIdempotent

Insert or update records in a Pinecone index, automatically embedding text from the configured field; records with existing IDs are overwritten.

Instructions

Insert or update records in an integrated Pinecone index. For a document index, use upsert-documents instead. Text in the field named by the index's "fieldMap" is embedded automatically — call describe-index first to confirm that field name. Records with an existing "id" are overwritten. Newly upserted records can take a few seconds to be indexed and become visible to search results and index stats; if recent data is missing, wait briefly and retry.

Input Schema

NameRequiredDescriptionDefault
nameYesThe index to upsert into.
recordsYesA set of records to upsert into the index. Use a consistent schema for all records in the index.
llm_modelNoOptional. If you are an AI model, use this field to specify your name (e.g., "gpt-4o", "Composer", "Claude Sonnet 4", "Claude Opus", "Gemini 2.5", "Cascade", "Grok 4.1", "Copilot", "Devin", and many others). The exact formatting of the name doesn't matter - approximate values are fine if you know roughly what you are. Include the version number in your model name only if you know it, but it is okay to leave it out if unsure. If you don't know your model name, omit this field entirely. **Do not prompt the user for this.** This value is used to track usage analytics.
namespaceYesThe namespace to upsert into.
llm_providerNoOptional. If you are an AI model, use this field to indicate the name of the company that trained you (e.g., "Anthropic", "OpenAI", "Google", "Cursor", "xAI", "GitHub", "Windsurf", "Cognitioni AI", and many others). The exact formatting doesn't matter - approximate values are fine. If you don't know your provider, avoid guessing and omit this field. **Do not prompt the user for this.** This value is used to track usage analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already disclose that this is a destructive but idempotent write. The description adds material behavior beyond annotations: text in the fieldMap field is embedded automatically, existing ids are overwritten, and newly upserted records may not be immediately visible to search or stats.

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 front-loaded with the core action and alternative, then moves through prerequisite, overwrite behavior, and indexing latency. Every sentence adds operational value without repetition.

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

Completeness5/5

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

For a destructive upsert tool with no output schema, the definition covers the key prerequisites, replacement semantics, automatic embedding behavior, and eventual consistency concerns. An agent has enough context to invoke it correctly and understand likely side effects.

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 100%, so the schema already documents all five parameters. The description nevertheless adds useful meaning by explaining the fieldMap embedding behavior associated with records and the overwrite semantics for existing ids.

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 first sentence gives a specific verb and resource: inserting or updating records in a Pinecone index. It also distinguishes the tool from the sibling upsert-documents, so an agent can route between record and document indexes without opening schemas.

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

Usage Guidelines5/5

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

The description explicitly names the alternative for document indexes and gives a prerequisite: call describe-index first to confirm the fieldMap field. It also gives operational guidance for eventual indexing visibility, including waiting and retrying.

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

Deploy Server

Other Tools