Plugin tracker

Tools

Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.

Latest snapshot2026-09-12USmethodology registry-public-v1

Searchable tools

113,018

Authless tools

7,424

Auth required

100,766

Described tools

61,167

119,491 tools

Delete Postdelete · Delete a post by ID. Use when the user says 'delete my last post', 'cancel that post', or 'remove the scheduled post'.PostifyPostifyPluginrequiredMarketing
Get Analytics Overviewget · Get workspace analytics (post counts, delivery rate, channel stats). Use when the user asks 'how did my posts perform', 'show analytics', or 'what's my delivery rate'.PostifyPostifyPluginrequiredMarketing
Get Postget · Fetch a single post by id, including its per-channel variants, schedule, and recurrence. Use to inspect one specific post before editing, rescheduling, or deleting it.PostifyPostifyPluginrequiredMarketing
Get Scheduleget · Read the user's scheduled posts inside a date window. Use for 'what's going out this week', 'is anything scheduled Thursday', 'show my queue for next week'. Prefer this over list_posts whenever the question is about a time period.PostifyPostifyPluginrequiredMarketing
List Connected Channelslist · List the workspace's connected social channels (platform, handle, connection status, follower count). Use when the user asks 'what channels are connected', 'which accounts do I have', or before posting to confirm a platform is live.PostifyPostifyPluginrequiredMarketing
List Postslist · List the user's posts, optionally filtered by status. Use when the user asks 'show me my scheduled posts', 'what's in my queue', or 'list my drafts'.PostifyPostifyPluginrequiredMarketing
Publish Post Nowpublish · PUBLISH a post PUBLICLY and IMMEDIATELY to its connected social channels. This goes live right away and is visible to the world — only use when the user explicitly asks to publish now. For anything tentative, use create_draft or reschedule_post instead.PostifyPostifyPluginrequiredMarketing
Reschedule Postreschedule · Reschedule a post to a new date/time. Use when the user says 'move that to Tuesday', 'reschedule for 3pm', or 'push it back a day'.PostifyPostifyPluginrequiredMarketing
Search API Docssearch · Search Postify's public API documentation: REST endpoints/operations, error (problem) codes, webhook event types, and permission scopes. Returns each match with its canonical docs URL. Use when the user asks how to call the API, what an error code means, which webhook events exist, or what a scope grants.PostifyPostifyPluginrequiredMarketing
Search Media Librarysearch · Search the user's OWN media library — the images THEY have already uploaded — and add a match to the post. Use this (NOT search_image) whenever the user refers to their own media: 'use a photo from my library', 'the image I uploaded earlier', 'find my logo', 'that product shot', 'pick one of my photos'. search_image is for brand-new STOCK photos; this is for the user's existing uploads.PostifyPostifyPluginrequiredMarketing
Suggest Optimal Posting Timesuggest · Suggest the best times to post for the target platforms, ranked from this workspace's own publish history and engagement (deterministic — no model call, no AI credits). Returns up to 3 suggestions per platform (platform, ISO datetime of the next occurrence, human-readable day/time, reason, 0-100 rank score) plus a `basis`: 'account_data' when the ranking is the workspace's own data, 'baseline' when it has too little history to personalize and a generic industry default was served instead. Report the basis rather than presenting a baseline as personalized. Changes nothing — pair with reschedule_post or create_draft to act on a suggestion.PostifyPostifyPluginrequiredMarketing
Create documentcreate · Create a draft Montra document in the connected workspace. Only call this when the user explicitly asks for a new document in this conversation — never on your own initiative.MontraMontraPluginrequiredDeveloper Tools
Create ticketcreate · Add a ticket to a Montra document. Only call this when the user explicitly asks you to add a ticket in this conversation — never on your own initiative, e.g. to break work down or log follow-ups. `body` is the ticket's markdown implementation spec; `summary` is the one-line gist shown next to the title.MontraMontraPluginrequiredDeveloper Tools
Delete ticketdelete · Remove a ticket from its Montra document. Only call this when the user explicitly asks you to delete that ticket — never to clean up work you consider finished, duplicated, or out of scope. The row is soft-deleted, so it stops appearing in the document but stays recoverable from the app.MontraMontraPluginrequiredDeveloper Tools
Get connected workspaceget · Show which Montra workspace this connection is bound to.MontraMontraPluginrequiredDeveloper Tools
Get documentget · Read one Montra document with its folder, its tickets (each ticket body is the markdown implementation spec), and the status of its latest generation.MontraMontraPluginrequiredDeveloper Tools
Get ticketget · Read one Montra ticket in full, including `body` — its markdown implementation spec. Document and ticket lists omit `body`, so fetch the ticket here before implementing it.MontraMontraPluginrequiredDeveloper Tools
Get ticket imagesget · Get the screenshots attached to a Montra ticket — real UI captures the person marked up while recording, so read them as part of the spec rather than as decoration. Each `url` is a short-lived signed link; fetch the images while you are working the ticket instead of storing the URLs.MontraMontraPluginrequiredDeveloper Tools
Get transcriptget · Read what the person said while recording, as the narration behind a document's tickets. Pass either a documentId for every transcribed input on the document, or a single inputId. This is supporting context: the tickets remain the spec.MontraMontraPluginrequiredDeveloper Tools
Link ticket to an external issuelink · Record where a Montra ticket now lives downstream — e.g. the Linear issue you just created from it — so the ticket shows a link back. Whenever the user asks you to create an external issue from a ticket, record it here as part of that export — no separate ask is needed. Do not call it for issues you did not create, and it is not a way to mark a ticket done. One link per ticket and provider; linking again re-points the existing one.MontraMontraPluginrequiredDeveloper Tools
List documentslist · List recent Montra documents in the connected workspace, optionally limited to one folder.MontraMontraPluginrequiredDeveloper Tools
List folderslist · List the folders in the connected workspace. Use a folder id to narrow list_documents.MontraMontraPluginrequiredDeveloper Tools
Read a Montra share linkget · Resolve a pasted Montra share link (montra.com/share/<token> or /tasks-for-agents/<token>) into its full machine-readable payload — document, tickets with markdown specs, annotated screenshot URLs, recordings, and agent instructions. Always use this instead of fetching or browsing the share web page. Works on any workspace, and on invite-only links too: when the link is not publicly readable it resolves as the Montra user who authorized this connection.MontraMontraPluginrequiredDeveloper Tools
Search the workspacesearch · Semantic search across the connected workspace's documents, tickets, transcripts, inputs, analyses, and folders. Hits are resolved to the real entity they belong to: each result is a ticket, document, or folder with its own title and verbatim body text. Results are ranked by relevance and limited to what the connected user can access.MontraMontraPluginrequiredDeveloper Tools
Update documentupdate · Replace the title and/or summary of a Montra document. Only call this when the user explicitly asks you to change them in this conversation — never on your own initiative, and never to note progress. Overwrites the stored values, including edits made by people.MontraMontraPluginrequiredDeveloper Tools
Update ticketupdate · Replace a Montra ticket's title, summary, or markdown body. Only call this when the user explicitly asks you to change the ticket's text in this conversation — never on your own initiative, and never to record progress (e.g. adding 'implemented', 'done', or '✅' to the title or body). The ticket is the person's spec; report progress in conversation instead. Each field you pass overwrites the stored value outright, so send the complete new text rather than a fragment or a diff.MontraMontraPluginrequiredDeveloper Tools
Add notespott · Create a note linked to one or more records (candidate, company, job, application, etc.). Supports @-mentions in content.SpottSpottPluginrequiredHR & Recruiting
Add records to listspott · Add one or more records to a named list (candidate pool, company list, or company-contact list). Lists are manual collections recruiters curate for targeted outreach or reporting.SpottSpottPluginrequiredHR & Recruiting
Complete taskspott · Mark a task as completed (or re-open it). Idempotent.SpottSpottPluginrequiredHR & Recruiting
Create applicationspott · Create an application linking a candidate to a job (standard) or directly to a company (speculative). Supply jobId OR companyId, not both.SpottSpottPluginrequiredHR & Recruiting
Create candidatespott · Create a new candidate manually with name and optional contact identifiers. Returns the new candidate id.SpottSpottPluginrequiredHR & Recruiting
Create companyspott · Create a new company (client) record with its core company info and optional pipeline stage. Returns the new company id. Check for an existing company first with spott_quick_lookup or spott_search_records to avoid duplicates.SpottSpottPluginrequiredHR & Recruiting
Create company contactspott · Create a new company contact (a person working at a company, e.g. a hiring manager, HR or BD contact): person details plus their role at that company. Use spott_create_candidate instead for job seekers. Spott also creates a linked candidate record backing the contact, so both ids are returned. Check spott_get_company_employees / spott_quick_lookup first to avoid duplicates.SpottSpottPluginrequiredHR & Recruiting
Create jobspott · Create a new job tied to a company. Returns the job id. Optionally seeds a briefing note from intake.SpottSpottPluginrequiredHR & Recruiting
Create opportunityspott · Log a business-development opportunity on a company: expected value, target stage, decision window.SpottSpottPluginrequiredHR & Recruiting
Create taskspott · Create a task with optional due date, assignee, and linked entities (candidate/company/job/etc).SpottSpottPluginrequiredHR & Recruiting
Enrich candidatespott · Kick off external enrichment (email, phone, LinkedIn, or full profile) for a candidate via the configured data provider. Returns the provider response or a delayed request id.SpottSpottPluginrequiredHR & Recruiting
Enroll candidates in campaignspott · Enroll one or more candidates into an outreach campaign. Accepts either campaignId or campaignName; the tool resolves the name to an id. Reversible (un-enroll via campaign management).SpottSpottPluginrequiredHR & Recruiting
Generate job descriptionspott · Have Spott generate a full job description for a job from its current fields. Creates the description record if one does not exist yet and kicks off generation. promptTemplateId defaults to the tenant default JOB_DESCRIPTION template if omitted.SpottSpottPluginrequiredHR & Recruiting
Get application activityspott · Fetch activity entries for an application: stage changes, interviews logged, scorecard submissions, comments added.SpottSpottPluginrequiredHR & Recruiting
Get application commentsspott · Fetch internal comments on an application. Page-paginated.SpottSpottPluginrequiredHR & Recruiting
Get candidate activityspott · Fetch recent activity entries (interactions, status changes, notes) for a candidate. Cursor-paginated.SpottSpottPluginrequiredHR & Recruiting
Get candidate applicationsspott · Fetch all applications a candidate has — both standard (linked to a job) and speculative (linked directly to a company).SpottSpottPluginrequiredHR & Recruiting
Get candidate certificationsspott · Fetch a candidate's professional certifications.SpottSpottPluginrequiredHR & Recruiting
Get candidate contact identifiersspott · Fetch all contact identifiers (emails, phone numbers, social profiles) for a candidate.SpottSpottPluginrequiredHR & Recruiting
Get candidate educationspott · Fetch a candidate's education history: schools, degrees, fields of study, dates.SpottSpottPluginrequiredHR & Recruiting
Get candidate email historyspott · List the email/SMS/WhatsApp interaction history with a candidate, newest first. Returns paginated UniboxInteractionDto items (subject, snippet, direction, timestamp). Use to scroll through prior conversation when the user asks "did I discuss X with Jean?" — combine with spott_get_notes_for_record for the full picture.SpottSpottPluginrequiredHR & Recruiting
Get candidate work experiencesspott · Fetch a candidate's full work history with stats. Returns roles, companies, dates, descriptions.SpottSpottPluginrequiredHR & Recruiting
Get company activityspott · Fetch recent activity entries (interactions, status changes, notes) for a company. Cursor-paginated.SpottSpottPluginrequiredHR & Recruiting
Get company employeesspott · List company contacts (hiring managers, BD contacts) tied to a company. Cursor-paginated.SpottSpottPluginrequiredHR & Recruiting

Tool Explorer FAQ

What is Tool Explorer?

Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.

How do category and verb filters work?

Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.

Why do auth requirements matter?

Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.