Skip to main content
Glama
jcalderonzumba

Perplexity Comet MCP

by jcalderonzumba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

comet_upload

Upload a local file to a file input on the current page to attach images or documents to forms, posts, or upload dialogs. Provide the absolute file path, with optional CSS selector.

Instructions

Upload a file to a file input on the current page. Use this to attach images, documents, or other files to forms, posts, or upload dialogs. The file must exist on the local filesystem.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesAbsolute path to the file to upload (e.g., '/home/user/image.png' or 'C:\Users\user\image.png')
selectorNoOptional CSS selector for the file input element. If not provided, auto-detects the first file input on the page.
checkOnlyNoIf true, only checks if file inputs exist on the page without uploading

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.6.2

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It discloses that the file must exist locally but doesn't mention behavior on missing file, size limits, or whether upload is synchronous. Minimal insight into side effects.

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?

Two sentences, front-loaded with purpose, no redundant information. Every sentence adds value.

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?

Adequate for a simple upload tool but missing behavioral details like error handling, return value, or whether upload completes before returning. No output schema, so description should cover these.

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 coverage is 100% with clear descriptions for each parameter. Description adds one extra constraint ('file must exist on local filesystem') but doesn't significantly enhance understanding beyond schema.

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 'Upload a file to a file input on the current page' with specific verb and resource. It distinguishes from siblings like comet_screenshot or comet_ask, as it's the only file upload tool.

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?

It provides examples of when to use (attach images, documents, etc.) and implies context (file input on page). No explicit alternatives mentioned, but sibling naming makes it clear this is the only upload tool.

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