Skip to main content
Glama
RPasquale

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

salesforce_bulk_query_create

Destructive

Creates a Salesforce Bulk API query job to efficiently export large data sets. Use this to start a bulk query operation and retrieve records in manageable batches.

Instructions

Run the salesforce domain agent action bulk_query_create.

Routes through the platform's domain-agent dispatcher under your JWT, tenant, and company scope.

Args: message: Free-text objective for the action. inputs: Optional JSON string of structured inputs for the action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputsNo{}
messageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • removedInput schema / properties / arguments
      Removed value: -{
-  "default": "{}",
-  "title": "Arguments",
-  "type": "string"
-}
    • addedInput schema / properties / inputs
      Added value: +{
+  "default": "{}",
+  "title": "Inputs",
+  "type": "string"
+}
    • addedInput schema / properties / message
      Added value: +{
+  "default": "",
+  "title": "Message",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations indicate destructive and non-idempotent behavior, and the description adds little beyond that—it mentions JWT/tenant/company scope but no side effects, asynchronous behavior, or what resources are affected. With annotations already covering the safety profile, the description provides minimal additional context.

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?

The description is concise and well-structured, with the action name first and a clear args section. It is not verbose and is easy to scan, though it sacrifices substance for brevity, which is acceptable for a wrapper but not for a functional description.

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?

For a tool that likely creates a bulk query and requires subsequent status checks (evidenced by sibling salesforce_bulk_query_status), the description omits the workflow, expected return, and any required follow-up. The presence of an output schema is noted but not described, and the lack of guidance on usage or lifecycle makes it incomplete.

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?

The description gives basic explanations for both parameters: message as 'free-text objective' and inputs as 'optional JSON string of structured inputs.' However, with 0% schema coverage, this is insufficient—there is no detail on expected format, how these are used by the action, or examples, so the agent is left with vague guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool runs a specific action ('bulk_query_create'), which is a clear verb+resource, but it does not explain what that action actually does—no mention of creating a Salesforce bulk query, its purpose, or its output. It distinguishes itself from siblings by name but not by function, so an agent cannot infer when it is the right choice.

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?

There is no guidance on when to use this tool versus alternatives like salesforce_bulk_ingest_create or salesforce_bulk_query_status. The description mentions routing through a dispatcher but gives no context about prerequisites, typical scenarios, or exclusions, leaving the agent to guess.

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