Skip to main content
Glama

LinkedIn MCP Server (Salesbot)

by cz.salesbot

approve_message

Idempotent

Approve a draft and hand it to the campaign executor for sending (respecting daily limits and allowed hours). Optionally pass edited_messages to overwrite specific drafts before approval. By default each draft is verified by a second-pass quality check (Czech vocative, hallucinations, prompt adherence) — set skip_gpt_check=true to bypass. If the quality check rejects the message, the draft is automatically sent back for a rewrite based on the feedback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skip_gpt_checkNoIf true, skip the gpt-5-nano quality check (default false).
edited_messagesNoOptional list of edits to apply before approving
campaign_contact_idYesUUID of the campaign_contact

TDQS

A4.6/5.0
Behavior5/5

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

Discloses key behaviors beyond annotations: respects daily limits and allowed hours, optional edited_messages overwrite, quality check with automatic rewrite. No contradiction with annotations.

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?

Three concise, well-structured sentences. Front-loaded with main action. No redundant information.

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

Completeness4/5

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

Adequately explains the approval process, optional edits, and quality check. Lacks details on return value or success state, but acceptable given no output schema and moderate complexity.

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?

Adds meaning to edited_messages and skip_gpt_check beyond schema descriptions. Schema coverage is 100% but description clarifies that edited_messages overwrite specific drafts and that skip_gpt_check bypasses quality checks.

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?

Clearly states 'Approve a draft and hand it to the campaign executor for sending' with specific verb and resource. Distinguishes from sibling 'reject_message' and other campaign tools by focusing on approval.

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?

Provides guidance on when to use the skip_gpt_check parameter and explains automatic rejection/rewrite behavior. Lacks explicit 'when not to use' but context is clear from sibling tool names.

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

All LinkedIn MCP Server (Salesbot) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools have distinct purposes, but there is some overlap among search tools (search_job_postings, search_google_xray, search_linkedin_people, search_web) and messaging tools (send_connection_request, send_linkedin_message, reply_to_chat). However, detailed descriptions clarify the differences.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (e.g., add_contacts_to_campaign, list_campaigns). No mixing of conventions.

Tool Count3/5

48 tools is high but justifiable given the broad domain (LinkedIn outreach, CRM, campaigns, job postings, etc.). However, some tools could be consolidated (e.g., multiple search tools).

Completeness5/5

The tool set covers the entire workflow: searching, connecting, messaging, campaign management, CRM operations (fields, stages, tasks, notes), job postings, and posting. No obvious gaps.

Resources