Skip to main content
Glama
754,287 tools. Updated 2026-11-07 03:33

"A server for job searching" matching MCP tools:

  • Fast code search across any public git repo. Returns file paths, line numbers, and code snippets with context. Supports regex, boolean queries, fuzzy matching, and structural filters (declarations, usages, strings, comments). Dependency/build directories excluded by default. Searching for leaked secrets? Call code_analyze instead and read security_summary — it runs a real secret and credential scanner over the whole repository, where searching for key prefixes like "sk-", "ghp_" or "AIza" only matches the spellings you happened to think of.
    ConnectorNo auth
  • Search JobYap job postings by natural-language query. Matches job titles, falling back to significant keywords when the full phrase finds little. Returns result ids, titles and citable URLs for use with fetch. For structured filtering (location, company, remote, freshness) prefer search_jobs.
    ConnectorNo auth
  • Update only the exact saved job preferences or weekly job-alert setting the authenticated job seeker asked for, after showing a before-and-after preview. This is private and reversible, so their own request for exactly this change or a later confirmation is enough. Pass expected_snapshot unchanged from the original get_my_job_preferences result. The server checks both saved preference records atomically so an older confirmation cannot override a newer unsubscribe or settings change; a conflict requires a new read and preview. Omitted fields are preserved; empty title/location/employment arrays clear those lists, and null clears minimum salary. Never infer updates from job searches, recommendations or conversation. If the user unsubscribed from all email, turning weekly alerts on does not resubscribe them. Set resubscribe_all_email to true only when the user explicitly asks to receive Account Executive Jobs email again; that also restores eligibility for broadcasts. After an uncertain result, call get_my_job_preferences and retry the exact original arguments only if the desired state is absent. It sends no email immediately and does not promise recurring delivery. The tool never changes product-update flags, profile/contact data, resumes, delivery history, or alert checkpoints.
    Connector
    Destructive
    OAuth
  • Refresh the short-lived download URL for an exact organization-owned portable template package receipt. Supply the receiptId from a ready import/export template job. Server verifies retained immutable package/document authority; never pass bucket keys or arbitrary archive URLs. Project-bound editors must also pass the exact ready export jobId for their bound source project and this receipt; an unrelated job or receipt refuses.
    ConnectorOAuth
  • Prepare an application to one of the caller's matched jobs: a resume and a cover letter are generated from the profile, and the application waits for the user to send it. It costs one credit and sends nothing to the employer. Call it without `confirmation_token` first: that returns the job, the cost and a token. Tell the user the job and the cost, and call again with the token only if they say yes. A token works once, for five minutes.
    ConnectorOAuth
  • Start a deep text exploration of conversation transcripts. Returns immediately with a job_id (status "pending"); long-poll perspective_await_job until status "ready" for findings with source citations. A sub-agent reads raw transcripts (exact phrases, multi-conversation patterns, deep reads). Prefer conversations_search for broad thematic/semantic questions, and conversations_data_analysis for quantitative counts. Omit filters to explore the full analysis corpus. Use filters only to establish a clear transcript boundary: conversation status, a creation-date range, or explicit conversation IDs. Use conversations_data_analysis first when a cohort must be identified from structured attributes, then pass the resulting conversation IDs here. A filtered job covers the complete filtered scope, not the complete perspective. Use for: - Exact mentions of words/phrases - Comparing conversation patterns across time - Reading full conversations with specific participants - Cross-referencing text patterns ("conversations mentioning X AND Y") - Interviewer approach or conversation flow Behavior: - Read-only against conversation data. - Open-world: runs an automated exploration agent in a durable background job using external services. - Each call starts a new job — not safe to retry blindly for the same query. - Typical flow: conversations_explorer → perspective_await_job (re-poll while pending). When NOT to use this tool: - Counts/distributions — use conversations_data_analysis. - Semantic themes without exact match — use conversations_search. - One known conversation id — use perspective_get_conversation. - Polling a previously-started job — use perspective_await_job.
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    面向 Codex、WorkBuddy 等 AI 工具的知你AI助手合并版 Skills,涵盖当前会话分诊、客户查询与画像、历史会话检索、客户分群和 API Key 用量查询,并连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服等渠道。
    MIT No Attribution
  • A
    license
    Not graded
    quality
    C
    maintenance
    这是面向智能运维场景的 MCP 工具服务,让 Agent 能够按需检索日志内容并获取主机与应用的监控指标数据。它把实时的日志与指标证据接入 Plan-Execute-Replan 诊断流程,从而支撑自动故障排查与根因分析。
    3
    MIT

Matching MCP Connectors

  • DESTROY: Tear down previously deployed infrastructure Destroys infrastructure by calling the Oracle destroy endpoint for a session that has a prior successful deployment. IMPORTANT: This starts a long-running job. Use tfstatus/tflogs to monitor progress. SINGLE-FLIGHT: only one TF job per session at a time. If another job is already in flight, tfdestroy returns tf_job_conflict with the live job_id — attach with tfstatus/tflogs, or pass force_new=true to override. REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: force_new (boolean, default false) - bypass the single-flight guard. Use only when the existing run is provably wedged. PREREQUISITE: The session must have a prior successful deployment with a project_id. After destroy completes, the session is kept for historical record but hasDeployment is set to false.
    Connector
    Destructive
    No auth
  • Remove the background from a single image, returning the subject isolated on a transparent background. Supply the source image (URL or base64); optionally set crop to trim the result to the content, and creative_edit (default true) for higher-quality output that may not match the input pixel-for-pixel - set it false when the subject must stay pixel-identical, e.g. an existing sprite you will animate. The job result is a single image result with a url (not an array). The image is uploaded and validated, and an image larger than 15MB is rejected with HTTP 400. Credits are held when the job is accepted and refunded if it fails or is cancelled. Use removeBackground for this dedicated cutout task; editImage can also remove backgrounds via a prompt but is better for broader edits, while createImage and generateWithStyle produce new images rather than process an existing one. Pass an optional request_id to tag the result so you can retrieve it later via listGenerations (type image). Async generation job: returns `{id, status}` - poll `getApiJob` (job and credit contract: see the server instructions). Credits: This endpoint consumes 0.5 credits per result.
    ConnectorNo auth
  • Record payment for an ACCEPTED job. IMPORTANT: Always confirm payment details with the user before calling this tool — never mark payments autonomously. Job must be in ACCEPTED status (use get_job_status to check). Crypto payments (usdc, eth, sol): provide tx hash + network → verified on-chain instantly, job moves to PAID. Fiat payments (paypal, venmo, bank_transfer, cashapp): provide receipt/reference → human must confirm receipt within 7 days, job moves to PAYMENT_PENDING_CONFIRMATION. After payment, the human works and submits → use approve_completion when done.
    ConnectorNo auth
  • DESTROY: Tear down previously deployed infrastructure Destroys infrastructure by calling the Oracle destroy endpoint for a session that has a prior successful deployment. IMPORTANT: This starts a long-running job. Use tfstatus/tflogs to monitor progress. SINGLE-FLIGHT: only one TF job per session at a time. If another job is already in flight, tfdestroy returns tf_job_conflict with the live job_id — attach with tfstatus/tflogs, or pass force_new=true to override. REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: force_new (boolean, default false) - bypass the single-flight guard. Use only when the existing run is provably wedged. PREREQUISITE: The session must have a prior successful deployment with a project_id. After destroy completes, the session is kept for historical record but hasDeployment is set to false.
    Connector
    Destructive
    No auth
  • Set whether a PUBLISHED job is in the candidate's saved list (idempotent desired-state, NOT a toggle — pass saved:true to bookmark, saved:false to remove). Returns NOT_FOUND for a missing or non-public job.
    ConnectorNo auth
  • Retrieve the name and description of the company behind a job, by job ID. Use this tool when users want more detail about a company than search_jobs/get_job_details return (e.g. after finding a job and wanting to know more about the company that posted it). DO NOT use for: searching/discovering companies or jobs by keyword (use search_jobs instead). LLM USAGE INSTRUCTIONS: - The typical flow is: search_jobs to find jobs -> user picks one -> offer to look up the company -> if the user agrees, call this tool with that same job_id (the same guid used for get_job_details; no separate lookup step is needed first). - Do not call this automatically right after get_job_details; ask the user first unless they already explicitly asked for company details. - Not every company has published an employer branding profile, and some profiles are marked not visible by the company. When that happens this tool does NOT raise — it returns a Company with `message` set and empty name/desc. Relay that message to the user (e.g. "Looks like that company hasn't published a public profile.") rather than treating it as an error. Args: job_id: The unique identifier of the job whose company to look up (required). This must be the job's `guid` field from a search_jobs result, NOT its `id` field — `id` is a different, internal identifier that this tool does not accept. Returns: Company: Contains: - name: The company name (empty if message is set) - desc: The company description (empty if message is set) - message: Set instead of name/desc when there is no visible company profile to show; None when name/desc are populated Raises: Exception: If the job is not found, an API call itself fails (network error, non-200 response, GraphQL errors), or input validation errors occur
    ConnectorNo auth
  • Resolve a city or airport name or code before searching flights. Returns typed values such as city:SHA to search every catalog airport in Shanghai or airport:SHA for Hongqiao only. Pass the selected value unchanged to search_flights. Ask the traveler when multiple results are plausible.
    ConnectorNo auth
  • Use this when keyboard_walk, simulate_condition, screen_reader_transcript or check_page_alt_text returned a job id instead of a result — never abandon the check, collect it here. Pass the job id the tool returned; if it is still running, call again in a few seconds. The payload is identical to the one the tool would have returned inline — the same fields, the same caps, the same void handling — so nothing has to be parsed differently because a page was slow. The per-response options below are read from this call rather than from the queued run, so a job can be collected with more detail than it was asked for without paying for a second browser run. Read-only.
    ConnectorAPI key
  • Pick the correct New Zealand tax code for an IR330, and explain why. Use for: 'what tax code should I use', 'M or ME tax code', 'secondary tax code NZ', 'SB S SH ST SA which one', 'tax code for second job', 'am I on the wrong tax code'. THE WRONG CODE IS ONE OF THE FEW PAYROLL MISTAKES THAT COSTS MONEY QUIETLY ALL YEAR, and there are two ways to get it wrong. A SECONDARY CODE IS CHOSEN ON TOTAL INCOME ACROSS ALL JOBS, NOT ON WHAT THE SECOND JOB PAYS. Someone earning $60,000 in a main job and $8,000 in a second is SH, not SB. Choosing on the smaller figure under-taxes and produces a bill at year end. ALWAYS ASK FOR TOTAL INCOME before answering a secondary code question. If total_income_all_jobs is omitted this falls back to this job's income and returns a warning saying the band is very likely wrong; pass that warning on rather than reporting the code as settled. ME IS NOT SIMPLY "M PLUS A CREDIT". The Independent Earner Tax Credit, worth up to $520 a year, is withdrawn by receiving Working for Families, a main benefit or NZ Super, so someone inside the $24,000 to $70,000 band can still correctly be an M. Add SL when a student loan is being repaid. On a SECONDARY job the repayment is 12% of the gross with no threshold at all, because the repayment threshold belongs to the main job. That catches people who expect the threshold twice. Special tax codes, non-resident status and multiple secondary jobs are out of scope here; those need Inland Revenue. Args: annual_income: Income from THIS job, before tax. job_type: primary for the main job, secondary for any other. total_income_all_jobs: Total across every job. Needed for secondary. has_student_loan: Whether a student loan is being repaid. receives_wff_benefit_or_super: Working for Families, a main benefit or NZ Super. Any of these removes IETC eligibility. Returns: The code, what it means, why it applies rather than the alternative, the flat rate for a secondary code, and any warning about the inputs.
    ConnectorNo auth
  • Poll a job until it finishes — call this after document.process or dataset.build (Step 2). Call repeatedly every 3–5 seconds until status is 'completed' or 'failed'. For data_process jobs: the completed response includes execution_id — pass it to job.result. For dataset_build jobs: the completed response includes dataset_id — pass it to dataset.export. Args: job_id: Job ID returned by document.process or dataset.build.
    ConnectorNo auth
  • Read-only. The answer itself: typed facts, evidence excerpts, timestamps, confidence scores, freshness, and an explicit list of what could not be verified. Free, and safe to call repeatedly. If the job is not final yet the response is provisional (http_status 202) - poll until 200, or watch get_verification_status for a terminal state first. A completed job answers every required criterion; a partial one answers some and says so in limitations.
    ConnectorNo auth
  • Search the index of open job postings. Use for a one-off question about the job market: who is hiring for a role, what is open in a city or country, which companies have remote positions. Returns a page of job records plus a `meta.next_cursor` to continue; each record has title, company, structured locations, remote flag, employment type, salary when the board publishes one, and an apply URL. Descriptions are omitted unless `include_description` is set, because they are large. To find what has *changed* since you last looked, use job_changes instead — do not poll this tool in a loop.
    ConnectorNo auth
  • [FREE ACTION] Claim an open job from the AgentWorld job board. Provide your agent name and a valid Base L2 wallet (0x...) to receive USDC payout. Only one agent can claim each job. Once claimed, complete and submit within 7 days. Use browse_jobs() first to find open job IDs. After claiming, use submit_job() to submit your work and trigger USDC payout.
    ConnectorNo auth
  • Cancel a job the caller can access by its id (recovers a mistaken or duplicate submission). An API token can cancel any job in its organization, so an id from list_jobs may belong to a human teammate — cancel only a job the user explicitly identified. Only jobs still in PENDING state can be cancelled; a job already PROCESSING or COMPLETED returns an error — poll get_job first if unsure. Refunds the credit only if the job had not started processing.
    ConnectorOAuth
  • [FREE ACTION] Claim an open job from the AgentWorld job board. Provide your agent name and a valid Base L2 wallet (0x...) to receive USDC payout. Only one agent can claim each job. Once claimed, complete and submit within 7 days. Use browse_jobs() first to find open job IDs. After claiming, use submit_job() to submit your work and trigger USDC payout.
    ConnectorNo auth