get_skill_guideReturn the best-practice guide for a Sliq workflow — read and follow it
before acting on that workflow. skill selects the guide.
| Name | Required | Description | Default |
|---|---|---|---|
| skill | Yes | ||
| on_behalf_of | No | An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account. |
Changes observed during successful MCP inspections.
Input schema / properties / on_behalf_ofAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}Input schema / properties / skill / enumPrevious value: -[
- "blog_content_calendar",
- "blog_post_writing",
- "company_monitor",
- "email_inbox_management",
- "email_sequence_setup",
- "exa_find_people",
- "find_companies_news_scan",
- "find_companies_news_scan_setup",
- "find_companies_search_criteria",
- "find_companies_webset_mode",
- "find_people",
- "find_warm_intro_paths",
- "linkedin_flowless_campaigns",
- "linkedin_outreach",
- "linkedin_outreach_debugging",
- "linkedin_outreach_finding_leads",
- "linkedin_outreach_operations",
- "linkedin_outreach_warmup",
- "linkedin_post_monitoring",
- "linkedin_post_writing",
- "message_tagging",
- "mixed_channel_outreach",
- "news_scan_predictleads",
- "news_scan_tavily",
- "news_scan_theirstack",
- "posthog_setup",
- "prospecting_agent",
- "scheduling_calendar_events",
- "segment_tagging",
- "social_listening",
- "trigger_code",
- "weekly_sales_review"
-]New value: +[
+ "blog_content_calendar",
+ "blog_post_writing",
+ "company_monitor",
+ "email_inbox_management",
+ "email_sequence_setup",
+ "exa_find_people",
+ "find_companies_news_scan",
+ "find_companies_news_scan_setup",
+ "find_companies_search_criteria",
+ "find_companies_webset_mode",
+ "find_people",
+ "find_warm_intro_paths",
+ "linkedin_flowless_campaigns",
+ "linkedin_outreach",
+ "linkedin_outreach_debugging",
+ "linkedin_outreach_finding_leads",
+ "linkedin_outreach_operations",
+ "linkedin_outreach_warmup",
+ "linkedin_post_monitoring",
+ "linkedin_post_writing",
+ "message_tagging",
+ "mixed_channel_outreach",
+ "news_scan_predictleads",
+ "news_scan_tavily",
+ "news_scan_theirstack",
+ "posthog_setup",
+ "prospecting_agent",
+ "scheduling_calendar_events",
+ "segment_tagging",
+ "trigger_code",
+ "weekly_sales_review"
+]Input schema / properties / skill / enumPrevious value: -[
- "blog_content_calendar",
- "blog_post_writing",
- "company_monitor",
- "creating_todos",
- "email_inbox_management",
- "email_sequence_setup",
- "exa_find_people",
- "find_companies_news_scan",
- "find_companies_news_scan_setup",
- "find_companies_search_criteria",
- "find_companies_webset_mode",
- "find_people",
- "find_warm_intro_paths",
- "linkedin_flowless_campaigns",
- "linkedin_outreach",
- "linkedin_outreach_debugging",
- "linkedin_outreach_finding_leads",
- "linkedin_outreach_operations",
- "linkedin_outreach_warmup",
- "linkedin_post_monitoring",
- "linkedin_post_writing",
- "message_tagging",
- "mixed_channel_outreach",
- "news_scan_predictleads",
- "news_scan_tavily",
- "news_scan_theirstack",
- "posthog_setup",
- "prospecting_agent",
- "scheduling_calendar_events",
- "segment_tagging",
- "social_listening",
- "trigger_code",
- "weekly_sales_review"
-]New value: +[
+ "blog_content_calendar",
+ "blog_post_writing",
+ "company_monitor",
+ "email_inbox_management",
+ "email_sequence_setup",
+ "exa_find_people",
+ "find_companies_news_scan",
+ "find_companies_news_scan_setup",
+ "find_companies_search_criteria",
+ "find_companies_webset_mode",
+ "find_people",
+ "find_warm_intro_paths",
+ "linkedin_flowless_campaigns",
+ "linkedin_outreach",
+ "linkedin_outreach_debugging",
+ "linkedin_outreach_finding_leads",
+ "linkedin_outreach_operations",
+ "linkedin_outreach_warmup",
+ "linkedin_post_monitoring",
+ "linkedin_post_writing",
+ "message_tagging",
+ "mixed_channel_outreach",
+ "news_scan_predictleads",
+ "news_scan_tavily",
+ "news_scan_theirstack",
+ "posthog_setup",
+ "prospecting_agent",
+ "scheduling_calendar_events",
+ "segment_tagging",
+ "social_listening",
+ "trigger_code",
+ "weekly_sales_review"
+]Input schema / properties / skill / enumPrevious value: -[
- "blog_content_calendar",
- "blog_post_writing",
- "company_monitor",
- "creating_todos",
- "email_inbox_management",
- "email_sequence_setup",
- "exa_find_people",
- "find_companies_news_scan",
- "find_companies_news_scan_setup",
- "find_companies_search_criteria",
- "find_companies_webset_mode",
- "find_people",
- "find_warm_intro_paths",
- "linkedin_flowless_campaigns",
- "linkedin_outreach",
- "linkedin_outreach_debugging",
- "linkedin_outreach_finding_leads",
- "linkedin_outreach_operations",
- "linkedin_outreach_warmup",
- "linkedin_post_monitoring",
- "linkedin_post_writing",
- "message_tagging",
- "mixed_channel_outreach",
- "news_scan_predictleads",
- "news_scan_tavily",
- "news_scan_theirstack",
- "posthog_setup",
- "prospecting_agent",
- "scheduling_calendar_events",
- "social_listening",
- "trigger_code",
- "weekly_sales_review"
-]New value: +[
+ "blog_content_calendar",
+ "blog_post_writing",
+ "company_monitor",
+ "creating_todos",
+ "email_inbox_management",
+ "email_sequence_setup",
+ "exa_find_people",
+ "find_companies_news_scan",
+ "find_companies_news_scan_setup",
+ "find_companies_search_criteria",
+ "find_companies_webset_mode",
+ "find_people",
+ "find_warm_intro_paths",
+ "linkedin_flowless_campaigns",
+ "linkedin_outreach",
+ "linkedin_outreach_debugging",
+ "linkedin_outreach_finding_leads",
+ "linkedin_outreach_operations",
+ "linkedin_outreach_warmup",
+ "linkedin_post_monitoring",
+ "linkedin_post_writing",
+ "message_tagging",
+ "mixed_channel_outreach",
+ "news_scan_predictleads",
+ "news_scan_tavily",
+ "news_scan_theirstack",
+ "posthog_setup",
+ "prospecting_agent",
+ "scheduling_calendar_events",
+ "segment_tagging",
+ "social_listening",
+ "trigger_code",
+ "weekly_sales_review"
+]Input schema / properties / skill / enumPrevious value: -[
- "blog_content_calendar",
- "blog_post_writing",
- "company_monitor",
- "creating_todos",
- "email_inbox_management",
- "email_sequence_setup",
- "exa_find_people",
- "find_companies_news_scan",
- "find_companies_news_scan_setup",
- "find_companies_search_criteria",
- "find_companies_webset_mode",
- "find_people",
- "find_warm_intro_paths",
- "linkedin_flowless_campaigns",
- "linkedin_outreach",
- "linkedin_outreach_debugging",
- "linkedin_outreach_finding_leads",
- "linkedin_outreach_operations",
- "linkedin_outreach_warmup",
- "linkedin_post_monitoring",
- "linkedin_post_writing",
- "mixed_channel_outreach",
- "news_scan_predictleads",
- "news_scan_tavily",
- "news_scan_theirstack",
- "posthog_setup",
- "prospecting_agent",
- "scheduling_calendar_events",
- "social_listening",
- "trigger_code",
- "weekly_sales_review"
-]New value: +[
+ "blog_content_calendar",
+ "blog_post_writing",
+ "company_monitor",
+ "creating_todos",
+ "email_inbox_management",
+ "email_sequence_setup",
+ "exa_find_people",
+ "find_companies_news_scan",
+ "find_companies_news_scan_setup",
+ "find_companies_search_criteria",
+ "find_companies_webset_mode",
+ "find_people",
+ "find_warm_intro_paths",
+ "linkedin_flowless_campaigns",
+ "linkedin_outreach",
+ "linkedin_outreach_debugging",
+ "linkedin_outreach_finding_leads",
+ "linkedin_outreach_operations",
+ "linkedin_outreach_warmup",
+ "linkedin_post_monitoring",
+ "linkedin_post_writing",
+ "message_tagging",
+ "mixed_channel_outreach",
+ "news_scan_predictleads",
+ "news_scan_tavily",
+ "news_scan_theirstack",
+ "posthog_setup",
+ "prospecting_agent",
+ "scheduling_calendar_events",
+ "social_listening",
+ "trigger_code",
+ "weekly_sales_review"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true is consistent with a retrieval tool, so no annotation contradiction. Beyond the annotations, the description adds genuine behavioral context that the call returns prescriptive content meant to be followed before acting, which shapes how the agent should treat the output. It does not cover failure behavior for an invalid skill or how large the returned guide may be.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no filler; the return value is front-loaded and the parameter note is appended where it belongs. Nothing here could be cut without losing information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only lookup with a single enum parameter, the description covers what it returns and the obligation to read it before acting. With no output schema, one could ask for more detail on the guide's structure or on invalid-skill handling, but nothing essential to correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 50%: `on_behalf_of` is well documented in the schema while `skill` has no description, only a 31-value enum. The description's '`skill` selects the guide' adds a small amount of meaning but does not explain what each enum value corresponds to beyond its self-descriptive name. Baseline 3 is appropriate given the enum carries most of the semantic weight.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Return the best-practice guide for a Sliq workflow') and ties the `skill` parameter to guide selection, so the agent knows exactly what comes back. It does not distinguish itself from adjacent guide-style siblings such as get_personalization_guide or get_writing_style_guide, which an agent must infer from name alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit usage instruction: 'read and follow it before acting on that workflow,' which tells the agent both when to call it and what to do with the result. It stops short of stating exclusions (e.g., which workflows have no guide, or when the other guide tools are preferred), so it is clear context rather than full when/when-not routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.