Skip to main content
Glama
ebragas

Recruit CRM MCP

by ebragas

log_meeting

Log a meeting with date, attendees, and description. Link to candidates, contacts, companies, jobs, or deals. Optionally send calendar invites.

Instructions

Log a meeting via POST /v1/meetings.

Dates use ISO 8601 (e.g. 2025-04-29T18:30:00Z). related_to is the primary anchor entity. Use associated to cross-link the meeting to additional candidates/companies/contacts/jobs/deals. attendee_users expects integer user IDs; attendee_contacts and attendee_candidates expect slug strings. reminder accepts: -1 (no reminder), 0, 15, 30, 60, 120, 1440 (minutes before). do_not_send_calendar_invites defaults to True — safe for historical logging; set False to actually send invites to attendees. description accepts Markdown — converted to HTML before POST so the Recruit CRM UI renders bullets/bold/links correctly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
start_dateYes
end_dateYes
related_toYesReference to a CRM entity for `related_to`-style linkage.
attendee_contactsNo
attendee_candidatesNo
attendee_usersNo
descriptionNo
addressNo
meeting_type_idNo
reminderNo
owner_idNo
associatedNo
do_not_send_calendar_invitesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
idYes
titleNo
urlNo
Behavior4/5

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

The description details important behaviors: ISO 8601 date format, attendee parameter types, reminder value range, calendar invite defaults, and Markdown conversion. With no annotations, this sufficiently discloses key operational traits.

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 front-loaded with the main purpose and follows with clear bullet-like details. Every sentence adds value, though it could be slightly more concise.

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?

The description covers core aspects like dates, attendees, and invites, but misses explanations for parameters like address, meeting_type_id, and owner_id. Given 14 params and nested objects, it is adequate but not fully complete.

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 only 7%, but the description adds meaning to many parameters: explains date format, attendee types, reminder options, do_not_send_calendar_invites, and description conversion. This compensates well for the sparse schema.

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

Purpose4/5

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

The description clearly states 'Log a meeting via POST /v1/meetings.' which is a specific verb+resource. While it doesn't explicitly differentiate from siblings like create_note or create_task, the purpose is unambiguous.

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 explicit guidance on when to use this tool vs alternatives. The description only mentions historical logging context for do_not_send_calendar_invites, but lacks when-to-use or when-not-to-use instructions.

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/ebragas/recruitcrm-mcp'

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